Roles And Access Behavior
C2 does not treat every action the same way. A person might be allowed to view a page but still not be allowed to change anything on it. That is normal.
This page explains how access decisions usually work so you can troubleshoot without guessing.
How Access Is Decided
When someone opens a staff page, C2 checks a few things:
- Are they signed in?
- Do they have the right role for that task?
- Is the feature turned on for the community?
- Is the community allowed to use that feature at its current size or plan level?
If the answer to any of those is no, the action may be blocked even though the page itself still opens.
Why Pages And Actions Can Behave Differently
This is the part that confuses most new users.
- A page can be visible because the person is allowed to look at it.
- Saving on that page can still fail because changing data needs stronger access.
- Draft items often need extra care, because they are not meant for everyone who can view published items.
Example: someone might be able to open the Events page, but only a smaller group can create or edit events.
Self-Service Actions
Some actions are meant for the person using the system, not for staff editing on their behalf.
Examples include:
- marking their own attendance
- viewing their own profile
- viewing their own applications
These actions are intentionally easier to access, because they are part of normal user self-service.
Integration Access
Some communities also use integrations. These are automated connections that act on behalf of a tool or service rather than a person.
Integration access is more restricted than normal staff access:
- it must belong to the correct community
- it must use the correct integration setup
- it cannot use every staff page the way a human can
- it must have a role that specifically allows what it is trying to do
If an integration stops working, the first thing to check is whether its role or community access changed.
Draft Content
Draft items are intentionally separated from published items.
That means:
- draft events may need special access
- draft campaigns may need special access
- published work and draft work may appear in different places
This is by design. It keeps unfinished work out of the main view until you are ready.
What To Check First
When access feels wrong, check these in order:
- Is the person signed into the right staff profile?
- Does their role include the task they are trying to do?
- Is the feature available in this community?
- Is the item a draft, a published record, or a self-service action?
- Is an integration trying to do something that only a human should do?