In Actionstep, you're able to set permissions for both individual users and groups of users, known as 'system roles'. You will find that the permissions you can set are going to be different depending on what Actionstep plan you are on.
In this article, you will learn more about the permissions within Actionstep and how they can be different for different Actinstep plans. There are several links to more detailed articles below.
Concepts that are used in Actionstep permissions
System Roles vs Individual Permissions
As you issue a login to a new user on Actionstep, you can choose what they are able to do in the system. Some permissions are set as you set up the login but most will be associated to a 'System Role' that you choose for that user.
A system role is one that is created or set in your Actionstep and you define what a user with that system role is able to do in Actionstep. By assigning a system role, you are defining most of what the user can do in Actionstep.
Some admins will set their Actionstep with system roles that match the job descriptions in their business (e.g., 'Paralegal', 'Lawyer', 'Partner', etc). Some will label their system roles based on what the user can do (e.g., 'User with no accounts', 'Estate matters only', etc)
Admin permission vs Non-Admin
Every Actionstep system will come default with a system role that is called "Administrator" this system role will have access to everything in Actionstep.
There will also be a system role called "User". A user system role will be able to access everything in Actionstep except the Admin screen. Effectively, they will not be able to change how the system is configured.
There is a permission you can assign to every individual user to "Allow this user to alter your subscription data?". This permission allows user to see your Actionstep subscription settings and issue and remove users from your account.
A user does not need to be an administrator to have this permission.
System Role Permissions
These permissions affect groups of users known as 'system roles'. You can provide or revoke differing levels of access on a huge number of 'system objects'. You can also edit these permissions on the basis of modules, such as workflows or trust accounting. For more information, please see this article.
These permissions affect users' access to different ares of the system by providing or denying outright access to the pages themselves. For more information, please see this article.