Administrators can manage user roles and permissions by navigating to Manage navigation at the top of the screen and to the Settings tab on the far right of the Manage dashboard. User roles and permissions should be defined for any user that will require the ability to manage, track, approve or report on any organizational information. Base users that do not require these permissions will not be assigned a permissions role.
To access your user roles and permissions select the Roles and Permissions in the left navigation of the Settings screen.
Community Spark Roles
Three default roles and permissions are provided to help define Community Spark access. All users are provided basic personal profile and activity accesses. Additional permissions must be applied to any users requiring additional access. Custom roles may be created if additional parameters outside of the default roles are required. Please refer to the Creating Custom Roles below for more details.
- Account Administrator - full account access
- Account CRA Managers - donations, loans, investments, board seats, tracking and organizations management
- Community Engagement Officer - board seats, tracking, organizations, donations, events, and sparks management
Note that the default system roles may not be modified.
Roles and Permissions Management
Once your users are added to your Community Spark account, you may begin applying default or custom roles to those individuals that require tracking and management access. Roles and permissions can be applied at the account level or for specified areas.
- Account Roles - account level roles are presented on the default Roles and Permissions screen. For each role you would like to apply to a user(s), type their name in the Add An Account ___ box at the bottom of the role. Select the users to give the specified role permissions by checking the box to the right of their name. To remove user access, click the "x" next to their name. Select Save Changes at the bottom of the screen to apply the role changes.
- Area Roles - permissions may be applied for specified Area locations to provide the ability to provide access control for users in specified areas. To set area roles and permissions, toggle to the Area Roles screen on the Roles and Permissions screen. First, select the area to apply the permissions access to, you may then apply the specified roles to users by typing their name in the Add A ___ box at the bottom of the role. Select the users to give the specified role permissions by checking the box to the left of their name. To remove user access, click the "x" next to their name. Select Save Changes at the bottom of the screen to apply the role changes.
Creating Custom Roles
Community Spark allows for additional flexibility for administrators to create custom user roles with specified permissions. Custom roles can be created for both the account and the area permission levels. To create a custom role:
- Select Add Role to the right of the Roles & Permissions screen.
- Specify the name of the role.
- Provide a short description of what the role's permissions will allow the user to do within Community Spark.
- If you would like the role applied at the account level, select the account access options (settings, manage users, manage roles, manage reports). Any role applied to an Area should not have any account-level access. Do not select any of the account options for custom Area roles and permissions.
- Select the ability to manage or view the information in each of the Community Spark features. Only select the features to which you would like the role to have access to.
- Select Save when finished.
If any account-level permissions (settings, manage users, manage roles, manage reports) were applied to the role, it will now appear only on the account roles. If no account-level permissions were applied, it will appear as an option on both the account and area roles.
A custom role may be modified once it is created by clicking on the Edit button to the right of the role listed under the Account Roles. Note that the default system roles may not be modified.