Guides
Team, roles and sign-in
Epic Context is invite-only, and each person has one role per organisation: viewer, member, admin or owner. People sign in with a passkey, an e-mail link or a password; what someone may do in a project follows from their role in its organisation.
There are no per-project roles to keep in sync. A person's role in the organisation is their role in every project of that organisation, the org project included.
The four roles
| Role | May |
|---|---|
| Viewer | Read the books, and leave messages and comments |
| Member | Everything a viewer may, and create and edit blocks, create projects, and share a page with a public link |
| Admin | Everything a member may, and invite people, manage members and invitations, erase blocks for good, lock and unlock blocks, create API keys, switch apps, editors and public links |
| Owner | Everything an admin may, and change or delete the organisation itself, or hand it to an admin |
Reviewing what people and AI wrote does not need a separate role: everyone who may edit sees the changes feed and can undo a change there.
Inviting people
Owners and admins invite from Settings › Organisation › Members & invites:
- Nobody can hand out a role above their own, and nobody is invited as owner: an organisation has one, and it changes hands by a hand-over.
- Everyone receives an invitation by e-mail, also someone who already has an account, and becomes a member only by accepting it. It is valid for seven days and works once.
Handing over and leaving
- The owner hands the organisation over to an admin, with Make owner in Members & invites. The new owner takes over; the old owner stays on as admin.
- Anyone can leave an organisation, with Leave beside their own name. The owner leaves only after handing the organisation over.
- Leaving or being removed revokes the API keys the person made in that organisation and withdraws the invitations they sent there. When an admin removes someone, they are told which shared secrets that person saw, such as a prototype's password or the widget token, so they can change them.
- A demoted admin's open invitations for roles they may no longer give are withdrawn.
The record
What owners and admins do to people and access is written down: role changes, removals, people leaving, invitations, API keys, apps switched or installed, hand-overs and sign-in help, each with who did it and when. Owners and admins read the record in Members & invites. It is kept after the organisation is gone, so even its deletion is on record.
Signing in
The sign-in page offers three ways in, for the same account:
- A passkey. The everyday way: your device's fingerprint, face or PIN. You add one after you are signed in, under Settings › You › Account.
- An e-mail link. How you sign in the first time, and on a device without your passkey. The link is valid for 24 hours and opens a confirmation page first, so a mail scanner that opens links cannot use it up.
- A password, if you set one under Settings › You › Account. It needs at least twelve characters, and common passwords or ones containing your e-mail name are refused. After ten wrong attempts the account is locked for fifteen minutes.
A session lasts thirty days.
When someone cannot get in
An owner or admin can help a member with a lower role from Members & invites:
- A temporary password that works for 24 hours, once. It is shown once to the admin and never mailed. Signing in with it opens no session: it leads to one step, Choose your own password, and only that step signs the member in.
- Unlock an account that was locked after too many wrong passwords.
- Sign out everywhere, ending every session of that person.
An admin can only do this for someone with a lower role than theirs in every organisation that person is in. Each of these actions is kept in the record.
Single sign-on
There is no SAML or LDAP sign-in. AI tools and suite apps sign in with OAuth through Epic Context itself; see Connect Claude, Claude Code or Cursor.
Next
Last updated: