The right hands on the right content

• Viewer: can see content and previews, but not change anything. Good for stakeholders and reviewers.

• Contributor: can create and edit drafts, but not publish. Good for writers, agencies, and freelancers.

• Editor: can edit and publish content, and manage releases.

• Admin: can do everything, including managing people and project settings.

Roles can be given to individuals, or to everyone at a company domain — for example, every @yourcompany.com account as a Viewer. These rules are enforced by the database itself, not only by the CMS interface.

Admins can also organize people into groups, such as “Agency partners” or “Legal reviewers”, and give each group a role across the whole project or for selected collections only. Access stays easy to manage as teams and partners change.

During a code freeze, a legal review, or a big launch, publishing can be locked on a doc, with a reason and an optional end date. The lock is visible to everyone, and lifts automatically when the date passes.

The activity log records who did what, and when: saves, publishes, releases, translation imports, data syncs, publishing locks, and sharing changes. Combined with version history, teams can always answer what changed, who changed it, and what it looked like before.

People sign in with their Google accounts, so access follows your organization’s existing account policies. Content is stored in your own Google Cloud project, and nobody outside your organization has access unless you grant it.