Roles And Permissions

Roles are the simplest way to control access in C2. A role is just a bundle of jobs a person is allowed to do. For example, one role might let someone manage events, while another might only let them view profiles.

If you are new to C2, start here. Good roles keep the platform easier to use, safer to manage, and easier to hand over when staff changes.

Before You Start

• Know which tasks the person should be able to do.
• Decide whether they need full control or only a small set of actions.
• Keep the admin role for people who truly need full access.

Workflow: Create A Role

Prerequisites

• You are allowed to manage roles.
• You know the purpose of the role before you begin.

Steps

1. Open Settings.
2. Go to Roles and choose Create Role.
3. Give the role a clear name, such as Event Staff, Recruitment Team, or Read Only.
4. Choose a short role key if your community uses them. Use something easy to recognise, like events or helpers.
5. Select the actions this role should be allowed to perform.
6. Save the role.

Expected Result

• The role appears in your role list.
• You can use it immediately when assigning staff members.

Common Issues

• The role name is too vague, which makes it hard to remember later.
• Too many permissions are selected at once, which makes the role risky to use.
• The role key already exists, so the save is rejected.

Workflow: Edit A Role

Prerequisites

• You can open the role you want to change.
• You are allowed to manage roles.

Steps

1. Open Settings.
2. Go to Roles.
3. Open the role you want to change.
4. Update the name, key, or permissions.
5. Save your changes.

Expected Result

• The role now reflects the new responsibilities you assigned.
• Anyone using that role will gain or lose access based on the changes you made.

Common Issues

• The role is already attached to active staff, so changing it may affect multiple people at once.
• The built-in admin role is protected, so it should only be changed when you are sure about the impact.

Workflow: Remove A Role

Prerequisites

• You are certain the role is no longer needed.
• No one depends on it for day-to-day work.

Steps

1. Open the role.
2. Check which staff members use it.
3. Remove the role only if it is safe to do so.

Expected Result

• The role is no longer available for future assignments.
• Staff who used that role may lose access to actions they relied on.

Common Issues

• Deleting a role too early can lock people out of tasks they still need.
• If you are unsure, leave the role in place and reduce its access instead.

Workflow: Assign A Role To Staff

Prerequisites

• You can see the person you want to update.
• You have permission to manage staff roles.

Steps

1. Open the role you want to use.
2. Choose the staff members who should receive it.
3. Review the list before confirming.
4. Apply the change.

Expected Result

• The selected staff members can now do the tasks covered by that role.
• Their new access should be visible the next time they open C2.

Common Issues

• A person does not seem to gain access right away. Ask them to refresh and check that they are signed into the right staff profile.
• Some people may need more than one role if they do several different jobs.
• If a person still cannot do something, check whether the role you assigned actually includes that task.

Good Practices

• Keep roles focused. One role should usually cover one job type.
• Use names that match real work, not internal jokes or shorthand.
• Review roles regularly so old access does not pile up.
• When in doubt, create a smaller role and expand it later.

Related Pages

• Roles And Access Behavior
• Personnel Workflows
• Errors And Troubleshooting