Teams, Roles & Membership
Aglyn has two kinds of people: your team (who build and manage the site) and site members (visitors who sign up to your site). Both are permission-aware.
Paid. Seats are metered per tier; see Billing & plans.
Team roles
- Invite teammates to a site and assign roles.
- Create custom roles with unique permission sets.
- Apply per-member overrides on top of a role.
- Permissions are enforced across the console's APIs and surfaces, and team members act in the owner's organization, not their own.
Organizations
Aglyn is built around organization workspaces: an organization subscribes once, owns
multiple websites, and shares media, plugins, dynamic data and billing across them. You
can belong to several organizations with a different role in each (owner, admin, editor,
viewer), and editors/viewers can be limited to specific sites. Each organization gets a
Slack-style workspace address (your-org.aglyn.com).
Every account operates inside an organization — solo accounts simply get a personal workspace automatically. The team features above keep working unchanged.
Three kinds of user
The Team table labels every row with its type, because the type — not the role —
decides which seat it uses. The same editor role is one or the other depending on
whether their reach is the whole organization or a list of sites:
| Type | Reach | Seat |
|---|---|---|
| Team manager | The whole organization | One of your team seats (managersPerOrg) |
| Site collaborator | Only the site(s) they're granted | A collaborator seat on each site they can reach — never a team seat |
| Site member | A published site, as a visitor with an account | None. Free and unlimited on every plan |
Pending invites carry the same label, so you can tell a pending manager from a pending collaborator before it's accepted.
Site roles
Every person with access to a site holds one of four site roles. Managers get
admin on every site in the organization; collaborators are given a role per site.
| Site role | Can edit content | Can publish | Notes |
|---|---|---|---|
| Viewer | No | No | Read-only |
| Author | Yes | No | Drafts and edits everything; nothing they do goes live |
| Editor | Yes | Yes | The usual working role |
| Admin | Yes | Yes | Also manages the site's people, domain and plugins |
Author is the role to give a client who should work on their own content without being able to put it in front of visitors. Concretely, an Author cannot:
- publish or unpublish a page, or change its address
- change which saved version a page, layout or component serves
- schedule any of the above for later
- publish, unpublish or schedule a collection entry
- delete a page, layout or component
- read the site's orders or its webhook signing secrets
Everything else is open to them: writing and designing pages, editing layouts and components, uploading media, drafting and editing entries, and saving as many versions as they like. Someone with a publishing role reviews the draft and publishes it.
This is enforced in the database itself, not just hidden in the console — an Author cannot publish through any route into Aglyn.
What a site collaborator sees
Someone invited to a specific site rather than the whole organization gets a console scoped to that site: they land on it when they sign in, and the organization pages — Team, Media, Data, Plugins, Marketplace, Billing, Settings — aren't part of their console at all. With access to more than one site, they get the sites list to choose from. Organization-wide members see everything as before.
Support is one of those organization pages, so a site collaborator raises problems with whoever invited them rather than with Aglyn directly — see Support & community. Quota warnings still reach them on their own site's pages, since a full site is a limit they will run into; the warning names the workspace admin to ask instead of offering an upgrade they cannot buy.
Site membership
- Visitors can sign in / sign up to your site.
- Member accounts are unlimited on every plan — including Free. Signups are never metered, capped, or charged per account.
- Gate screens as members-only so only signed-in members can view them.
- New members flow into your contacts CRM.
Seats
Seats cover your team only: organization seats (workspace-wide) and per-site collaborator seats (teammates limited to one site). Both are metered and enforced; buy seat add-ons to grow. Site member accounts — visitors who sign up to your published site — are not seats and are never capped. See Billing & plans.
Related
- Billing & plans
- Staff console (Aglyn staff only)