How permissions work
Audience: Everyone; partners and developers · Who can do this: — Where in the app: — Status: draft. Checked against the app's permission rules 2026-09-29 (after PR #401 and #403).
What each kind of person can do on ClawCamp, and why it's set up that way.
The roles
- Visitor: anyone not signed in. Can read public pages: events, chapters, the map, speakers, partners, and this guide.
- Member: anyone signed in. Can apply to start or join a chapter, submit events, and edit the events they created.
- Event host: someone added as a host on one event. A host given edit access can edit that event. It gives them nothing on any other event, and no role on the chapter.
- Co-captain: runs a chapter's events. Can add, edit and publish any of the chapter's events, and can step down.
- Captain: runs the chapter. Everything a co-captain can do, plus editing the chapter's page and managing its team.
- Admin: ClawCamp staff. Can do everything a captain can on any chapter, plus add someone to a team without an invite and see the admin-only pages of this guide.
Who can do what
| Action | Member | Host with edit access | Co-captain | Captain | Admin |
|---|---|---|---|---|---|
| Submit an event | Yes | Yes | Yes | Yes | Yes |
| Edit an event you created | Yes | Yes | Yes | Yes | Yes |
| Edit an event someone else created | No | That event only | Their chapter's | Their chapter's | Any |
| Publish an event | No, it goes to review | No, it goes to review | Their chapter's | Their chapter's | Any |
| Show, hide or remove hosts on an event page | Events they created | That event only | Their chapter's | Their chapter's | Any |
| Edit the chapter's page | No | No | No | Yes | Yes |
| Invite, promote, demote, remove or restore team members | No | No | No | Yes | Yes |
| Remove yourself from a chapter team | — | — | Yes | Yes | — |
| Add someone to a team without an invite | No | No | No | No | Yes |
| Edit this guide | No | No | No | No | Yes |
"Their chapter's" means events belonging to a chapter where that person is an active captain or co-captain.
Why it works this way
- Publishing needs a chapter role. Anyone can suggest an event, but only people accountable for a chapter (or ClawCamp staff) can put one live. Everything else waits in the review queue for an admin.
- Captains own the chapter; co-captains own events. Splitting it this way lets a chapter add helpers for events without handing over its page or its team.
- Host access is per event. Inviting a speaker or partner to help with one event never gives them a say over the chapter or its other events.
- Anyone can step down. Removing yourself from a team always works. If removing or demoting someone would leave the chapter with no captain, the site warns first and emails ClawCamp's admins, so no chapter is left without anyone running it. Removing a co-captain never triggers this.
- Admins settle disputes. If people disagree about who should be on a team, an admin can restore anyone and change any role.
Chapters can't be deleted from the site. If a chapter should close, ask ClawCamp.
For the details of each area, see Chapter team and captains, Manage an event and Hosts.