Skip to main content
Advanced Permissions

Configure more granular permissions for ultimate control of your workflows

Peter Novosel avatar
Written by Peter Novosel
Updated over a week ago

Solution Permissions are used to control which specific user - or Team of users - have access to individual Solutions. For those situations where Solution Managers require granular control over who can read, create, update or delete records, SmartSuite offers an Advanced level of Solution Permissions.

Unlike the other two available permission levels which offer unrestricted access to everyone or to specific Teams, Advanced permissions supports four different levels of access that can be granted to individual users or Teams.

Why would I want to use Advanced Permissions?

Advanced permissions support a wide variety of use cases, allowing Solution Managers to grant certain users anything from read-only to full access to the records in their Solution. This capability allows you to share important data across the organization, while still controlling who can update or delete the underlying records.

For example, Human resources might share an employee directory, ensuring that records were accessible but only changed by authorized personnel. Customer service staff can be given the ability to create and edit their own records, while preventing changes in records filed by their co-workers.

Where to Find Advanced Permissions Settings

Advanced permission options are available from each Solution's Permissions configuration page. It is easily accessed by following these steps:

  1. Access the Solution, ensuring that you are logged in as a Solution Manager or user with the Administrator role.

  2. Open the Solution options menu by clicking the arrow to the right of the Solution name.

  3. Click Permissions.

  4. Click on the third option labeled Advanced Permissions.

Configuring Advanced Permissions

Once you select the Advanced permissions option, you have to specify which Teams and Member profiles should be assigned specific permissions in the current Solution.

1 - Selecting Members or Teams

The Add Teams or Members input box allows you to display available Members and Teams - simply click on the one that you want to assign permissions to. If there are multiple individual members or Teams that should have the same permissions, you can just keep clicking to add to the list. Everyone will be granted the same selected permissions level after you select it in the next step.

You can also start typing and the listed Teams and Members will be filtered dynamically. If there are no matches you'll see a message like the one below - just backspace to remove search text until results re-appear.

Select someone accidentally? Just click the small X next to the name and the Member or Team will be removed.

2 - Choosing a Permission Level

Once you have selected your Members and/or Teams, pick the right permission level for them. You have four options:

  • Full Access. Users with this access level have full control over the Solution's content - they can view, create, update and delete all records.

  • Editor. Users with the Editor permission can create, update and delete their own records but are restricted to read-only access to all other records in the Solution.

  • Contributor. Contributors can view and create records, but can only edit existing records when they are included in an Assigned To field in the record. This permission is perfect for many workflows, assigning edit rights to specific individuals or Teams involved in a particular process.

  • Assignee. The Members or Teams can view and edit content they have been assigned, but cannot create, view, or edit any other content.

  • Assignee+. The Members or Teams can view and edit content they have been assigned and create new content that is auto-assigned to them, but cannot view or edit any other content.

  • Commenter. The Members or Teams can view all content but cannot create or edit any content.

  • Viewer. These users have read-only access to the Solution's records and are unable to create, update or delete. Note that viewers are allowed to comment on records.

Add the Permissions group

Once a permission level has been selected you're ready to add the permission setting. Just click Add and all the Members and Teams you selected will be assigned the chosen level of Solution permissions.

Changing or Revoking Solution Permissions

If you ever need to change or revoke permissions, just head back to the Solution Permissions dialog and follow these simple steps:

Modify Permissions

To change granted permissions, just find the Member or Team you would like to modify. The currently-assigned permission level will be displayed to the right. Select the desired setting and the permission level is immediately updated.

Revoke Permissions

To entirely revoke a Member or Team's permissions for the solution, just click the small X icon at the far-right side of the row - all permissions for the selected individual or Team will be immediately removed and they will have no access (not even read-only) to its content. (Note: it is possible that individual Members will still have access to the Solution if they are part of another Team that has permissions.)

Advanced Permissions Recommendations

Use the "Everyone" Team to Assign a Default Level of Permissions

The best use for the Everyone group is to assign it the Viewer role. This allows every user of the SmartSuite workspace to view and comment on records while ensuring that only select groups or individuals can add, modify or delete the content.

Use cases for this include:

  • Providing access to policy and procedures information

  • Sharing details about a project and its progress

  • Allowing users to reference an inventory item in a work request

  • Sharing details about corporate initiatives

  • ...and many more!

Use the "Contributor" Permission to Power Workflows

There are many instances where you might want a team to have access to everyone's data but to limit who can update individual records. The Contributor permission level, in conjunction with the Assigned To field type, give you a ton of flexibility to do just that.

Here's a typical scenario - a project manager has an Assigned To field in their Tasks table, and gives the Project Team Contributor-level access to the solution. The PM then creates tasks, selects the appropriate assignee for that task in the Assigned To field, and saves the record. Now only the selected team member can make updates to their assigned Task. Simple!

Assign Permissions to Teams Whenever Possible

Organizations change, priorities are modified, and people join and leave teams in what can seem like a constant flow. To avoid having to make numerous ongoing changes to Solution permissions, assign users to Teams that are responsible for different functions.

You could assign a Team called "Sales Managers" to the "Full Access" permission level in your Sales Opportunities Solution. Then when you hire a new manager, just add them to the Sales Managers Team and they'll automatically be granted the appropriate access (perhaps along with read-only access to the Marketing Resources and HR Solutions, and so on...)

Related Video Content

Did this answer your question?