Users

The SG-Admin Users module — per-site users, roles, permissions, invitations.

The Users module in the admin is the per-site user administration surface. Operators add users, assign per-site roles, and manage permissions here. Account-tier user invitations live at SG-Dashboard; per-site grants happen here. This page is the Reference definition.

>

What is this for?

Read this page when you want the structural definition of per-site user administration — the role model, the permission scope, and the invitation flow.

Good use cases

• You are scoping editorial team access for a site.
• You are explaining the difference between account-tier and site-tier users.
• You hit a "how do I give an editor access to one site only?" question.

What NOT to use this for

• Step-by-step procedures — open the relevant Guide.
• Account-tier user invitations — open SG-Dashboard Invite Users.
• Per-release shipped change — open What's New or Changelog.

How this connects to other features

• SG-Admin Overview — parent surface.
• SG-Dashboard Overview — account-tier user surface.

Where to find it

Open SG-Admin for the active site. Users is in the sidebar under the settings group. The per-site grant list, add-user action, and role assignment are all reachable from this section. Admin access is required to grant, change, or revoke per-site roles.

Definition

The Users module administers the per-site user grant set. Each grant binds a user identity (account-tier) to a per-site role. The role determines what the user can do inside the admin and SG-Builder for that specific site.

The defining property is per-site scope. A user can have different roles across different sites under the same account.

Purpose

Define per-site user administration as a Reference layer.

Scope

Covers the role model, permission scope, and invitation flow. Does not cover account-tier user identity (SG-Dashboard) or per-step procedures (Guides).

Role model

Admin

Full access to every SG-Admin module and SG-Builder for the site. Can grant access to other users.

Editor

Content + composition access. Can edit and publish records, compose pages in SG-Builder. Cannot change site-level configuration or grant access.

Author

Content access only. Can create and edit own records; publish typically requires editor or admin sign-off depending on workflow configuration.

Read-only

Inspect-only access. Useful for stakeholders who want visibility without write capability.

>

Invitation flow

Account-tier invitations send the email and create the user identity. Per-site grants assign the role for one specific site. An operator with multi-site access shows up in the Users list of every site they were granted to.

Constraints and boundaries

Users is a Reference area for per-site user administration.

Do not use this Reference for: account-tier identity management (SG-Dashboard), per-step grant procedures (Guides), per-release shipped change.

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — Operator grants editor role to a new editor

Operator opens Users, clicks Add user, picks the user from account-tier identities (or invites them via SG-Dashboard first), assigns Editor role.

Example 2 — Operator changes a user's role

Operator opens Users, clicks the user, changes role from Author to Editor. The user's permissions update on next login.

Example 3 — Operator revokes access

Operator removes the user from the site's Users list. The user retains account-tier identity but loses access to this specific site.

Documentation guidance

Use this page as the structural definition for per-site user administration.

Reading order

Open this page when scoping editorial team access. Pair with SG-Dashboard Reference for account-tier identity.

Related reading

• SG-Admin Overview — parent surface.
• SG-Dashboard Overview — account-tier user surface.

Vocabulary cross-reference

• User is an account-tier identity.
• Grant is a per-site role assignment.
• Role is one of admin / editor / author / read-only.
• Invitation is the account-tier email that creates a new user identity.

Maintenance discipline

When Users module changes across releases (new role, new permission scope, new invitation flow), update this Reference.

Related reading