UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

Team

Team roles

What owners, admins, editors and viewers can do in Ulika, with the exact permission table, and the safety rules that stop you from locking yourself out.

Last updated October 11, 2026

Everyone who works in an Ulika workspace has exactly one of four roles: Owner, Admin, Editor or Viewer. The role decides what the person can see and change, and it applies to every project in the workspace. There are no per-project or per-page permissions.

Roles are enforced on the server, not just hidden in the interface. A viewer who somehow sent a "publish" request would be refused with a message such as "Viewers cannot publish changes."

The four roles at a glance#

RoleIn one sentence
OwnerEverything an admin can do, plus owning the workspace: only owners can add, demote or remove other owners.
AdminRuns the workspace day to day. Admins connect websites, manage projects, publish and manage the team, but cannot change owners.
EditorCan edit content and publish changes to production. Editors never need access to your code.
ViewerCan preview content but cannot make or publish changes.

If you are choosing a role for a new teammate, Editor is the right answer for anyone who writes copy or swaps images. Use Viewer for people who only need to look (a client who wants to follow along, a stakeholder, a developer who is reviewing). Use Admin for the people who help you run the workspace: they can connect sites and manage the team. Keep Owner for the one or two people who must always be in control, since only an owner can add, demote or remove an owner.

Permissions#

This table is the complete list of what Ulika checks. A check mark means the role can do it.

What you can doOwnerAdminEditorViewer
View content, preview the site, browse the media library and collectionsYesYesYesYes
Edit content (text, links, images, styles, page SEO fields) and use the AI assistantYesYesYesNo
Publish changesYesYesYesNo
Upload images and videos to the media libraryYesYesYesNo
Delete mediaYesYesYesNo
Add, change and delete collection itemsYesYesYesNo
Restore an earlier version from HistoryYesYesYesNo
Connect a website, create a project, approve a CLI or AI agent loginYesYesNoNo
Change project settings, disconnect a repository, delete a project, rename the workspaceYesYesNoNo
Manage the team (invite, change roles, remove people, revoke invitations)YesYesNoNo
Make someone an owner, or change or remove an ownerYesNoNoNo

A few details that the table cannot show:

  • Restoring and publishing. Restoring a version and publishing it in one step needs both the restore permission and the publish permission. Editors and owners have both.

  • Connecting a website is for owners and admins. Connecting adds a connector to your repository and links your hosting, so it is treated as an administrative action. An editor who opens the connect screen sees "Only owners and admins can connect a website".

  • Agents. When an owner approves an AI agent or a machine for the CLI, that credential is separate from any person's role. See Security and privacy.

What a viewer sees#

A viewer can open every project and every screen, but the controls that change things are off:

  • A bar at the top of the app reads You have view-only access. Ask an owner or admin for edit access.

  • The media library says "Viewers can browse the library but cannot change it."

  • Collections say "Viewers can read collections but cannot change them."

  • Page SEO fields say "You have view-only access, so these fields are read-only."

  • Settings controls are disabled with a tooltip such as "Only owners and admins can manage the team."

Changing a role#

Owners and admins can change roles. Admins cannot touch owners: they cannot make anyone an owner, and they cannot change or remove one.

  1. Open Team from the workspace header, the account menu, the project sidebar or the command menu (Team and invitations). It opens the Team section of Workspace settings.

  2. In the Role column, open the dropdown on the person's row and pick Owner, Admin, Editor or Viewer. Admins see Owner greyed out.

  3. A confirmation appears, for example "Dana is now editor".

Owners can promote an existing member to owner here. You cannot invite someone as an owner directly; invitations are for admins, editors and viewers only (see Inviting people).

Rules that protect the workspace#

  • You cannot change your own role. Your dropdown is disabled with the message "This is you. Ask another owner or admin to change or remove your access." This is how an owner could otherwise lock themselves out.

  • Only an owner can change or remove an owner. An admin sees an owner's role and actions disabled with "Only an owner can change or remove an owner." Admins also cannot transfer ownership.

  • A workspace needs at least one owner. Demoting or removing the last remaining owner is refused with "A workspace needs at least one owner." Promote someone else first.

  • CLI logins are re-checked. When a person's role changes, any CLI session that person approved on a machine is revoked, so a cached "owner" role cannot outlive the change. They run ulika login again to approve the machine once more.

Removing a member#

Owners and admins can remove people (admins cannot remove an owner), and nobody can remove themselves.

  1. In Team, open the Actions menu (the three dots) on the person's row.

  2. Choose Remove from workspace.

  3. Type the person's name to confirm, then choose Remove member.

The person loses access to every project in the workspace immediately. Content they already published stays exactly where it is. Their CLI sessions are revoked, and agents they approved are revoked when their membership ends. They can be invited again later.

Who can do what: common questions#

  • Can an editor publish? Yes. Editors and owners can publish. Viewers cannot.

  • Can an editor connect a new site? No. That needs an owner or an admin.

  • What is the difference between an owner and an admin? Admins can do everything for running the workspace. Only owners can add, demote or remove owners.

  • Can I give someone access to one project only? No. Roles apply to the whole workspace.

  • Can a viewer see drafts? A viewer can look at the project, but cannot edit or publish. Drafts stay in Ulika until an editor or owner publishes them.

Related#

  • Inviting people: send email invitations, resend, revoke and understand expiry.

  • Publishing: what happens when an editor or owner publishes.

  • Security and privacy: how accounts, tokens and permissions are protected.

Was this page helpful?

PreviousWhen a publish failsNext Inviting people

On this page

  • The four roles at a glance
  • Permissions
  • What a viewer sees
  • Changing a role
  • Rules that protect the workspace
  • Removing a member
  • Who can do what: common questions
  • Related
Ulika documentationFAQ · CLI reference · Terms · Privacy