Why can't I do something my role should allow?
Common reasons a member cannot open Settings, a portal, or an action, and what each error message means.
Use this article to troubleshoot when a member cannot open an admin page, a shared workspace, or an action they expected to work.
Most access problems in Clipido come down to group membership, portal authentication settings, or whether the member signed in through the right URL. Clipido uses groups rather than per-action role pickers on the Members page.
I cannot open Settings or admin pages
Only members of the "Admin" group can open Settings and manage "Members" or "Groups". If someone is in a custom group only, they can sign in to Clipido but will not see admin areas.
If they try to open a restricted admin URL, they may see "Sorry, but you don't have permission to access this page." Individual actions can show "You don't have permission to perform this action" or a tooltip reading "You don't have permission to view this."
Fix: On Settings → Members, move the person into the "Admin" group, or have an existing admin perform the task.
I am in a group but cannot open a shared workspace or gallery
Group membership alone does not open a portal. The portal must use "Private" authentication and link that group on its "Publish" panel.
Check these points:
- Open the shared workspace or gallery in "Sharing → Publish → Authentication".
- Confirm Auth method is "Private", not "Public" or "Login required".
- Confirm the member's group appears under "Members" on that panel.
- If the list is empty, add the group with "Add access group".
If authentication is "Private" and no groups are linked, the editor warns "No one will be able to access this portal until you add at least one access group."
Members of the "Admin" group can open any private portal even when their custom group is not linked.
I signed in but Clipido says I have no account
Domain invites and email invites only apply when the person signs in through the correct entry point.
- "Email invites" activate when the person signs in with the invited email address.
- "Domain invites" auto-add people whose email matches a whitelisted domain, but only when they sign in through your club's sign-in URL. Signing in at the generic Clipido login page does not auto-join every matching domain.
If someone uses the wrong sign-in URL, Clipido may show that no account exists for them even though an invite or domain rule is configured.
I cannot edit or remove a SCIM member
When SSO and SCIM are enabled, some members are provisioned from your identity provider. Those rows show a "SCIM" badge on Settings → Members.
For SCIM-managed members:
- "Edit groups" is disabled. The tooltip reads "This member is managed by SCIM. Group membership cannot be changed here."
- "Remove" is disabled. The tooltip reads "This member is managed by SCIM. They cannot be removed from the workspace here."
Change SCIM membership in your identity provider, not in Clipido Settings.
A feature shows upgrade or not enabled
Some capabilities use two separate gates: whether the feature is on your plan, and whether an admin turned it on in Settings.
| Message pattern | What it means | What to do |
|---|---|---|
| Upgrade button or "upgrade to access" | The feature is not on your plan | Request the add-on (for example Multiple group membership or SSO / SCIM on Settings → Advanced) |
| "feature is not enabled" | The plan includes it, but the toggle is off | An admin turns it on under Settings → Advanced or the relevant feature settings page |
Do not request an upgrade when the real blocker is a toggle that an admin can enable locally.
I expected granular permissions that are not there
Clipido's current admin permission model is binary: members are either in the "Admin" group or they are not. Custom groups control portal entry when linked, not individual admin actions like approving uploads or editing tagging forms.
If someone needs admin capabilities, add them to the "Admin" group. If they only need to view files in a shared workspace, keep them in a custom group and link that group on the portal's "Publish" panel instead.