In LiKE, a person's access is determined by two independent roles, not one:

Organization role
Standing within the team overall: managing people, spaces, settings, and the plan.
Space role
What you can do with the content of a specific space: read or edit.

The same person can be, for example, a User in the organization but an Admin in the "Marketing" space and a Viewer in "Development". The "User" role in the organization does not mean "cannot edit" — everything is decided by the role in the specific space.

#Organization role

Owner Admin Editor User Guest
Role Purpose
Owner One per organization. Full access to everything, including the plan, payment, and deleting the organization. Sees and manages all spaces.
Admin Manages the organization: the team, spaces, integrations, settings, domain. Sees and manages all spaces. Does not manage the plan and payment, and does not connect SSO (can only edit an already configured one).
Editor Creates and edits articles — but only in the spaces where they have the Editor or Admin role. Uses import. Does not see analytics (it's available from the Admin level). Does not get automatic access to all spaces.
User A basic employee: search and reading. Can edit only in spaces where they have been explicitly granted the space Editor or Admin role.
Guest The most restricted level — for external or temporary participants. Search and reading in the granted spaces.

Key difference: only the organization Owner and Admin have blanket access to all spaces. For an Editor, User, and Guest, access to each space is determined by their role in that space.

#Space role

Assigned separately in each space and independent of the organization role.

Admin Editor Viewer Access restricted
Space role Capabilities
Admin Full control of the space: articles, settings, and managing space members.
Editor Creating, editing, and deleting articles within the space.
Viewer Reading the space's articles only.
Access restricted An explicit revocation of access to a corporate space for a specific person (see "Special cases").

#How roles combine

When accessing a space's content, the check goes as follows:

  1. Organization Owner or Admin — access is always granted, no space role required.
  2. Otherwise (organization Editor / User / Guest) — the space role decides: you need a role no lower than required.
  3. No access to the space — you'll see a "no access" message (we don't even reveal the existence of others' content).
Examples:
  • An organization User with the space role Editor fully edits articles in their space.
  • An organization Editor who has the Viewer role or "Access restricted" in a space cannot edit there: the organization role doesn't override the space role.
  • An organization Admin edits in any space, even if not explicitly added to it.

#Who can do what

"Editor+ in the space" below means: the Editor or Admin space role — or an organization Owner / Admin (they always pass).

Action Who can do it
Searching and reading published articles Any member with access to the space (public ones — even without logging in)
Open an article in the editor, collaborative editing Editor+ in the article's space
Save an article (manually or via autosave) Editor+ in the article's space
Create / move / copy / delete / merge an article Editor+ in the involved spaces
AI tools on an article (improve, rewrite, translate, assess quality) Editor+ in the article's space
AI on free text (AI author, formatting) and @-mentions Organization Editor — or Editor/Admin in at least one space
View, invite, and change roles of space members Space Admin — or organization Admin / Owner
Assign a member as Space Admin Only the organization Owner or Admin
Creating, deleting, and restoring spaces Organization Owner or Admin
Managing the organization: team, integrations, settings, domain Organization Owner or Admin
Connecting and removing SSO (single sign-on) Only the Owner (the Admin can edit an already configured SSO)
Plan, payment, deleting the organization Only the Owner

#Special cases

  • Personal spaces. Every user has a personal space ("My space") visible only to them — even the organization Admin doesn't see others' personal notes.
  • Public access. Anonymous visitors see only articles in public spaces with the "Published (public)" status. No role is required for this — see details in the Public knowledge base article.
  • Search — within a single space. At any moment, search works in the context of the selected space; switch via the space switcher in the sidebar. This is a deliberate decision for the sake of answer quality and privacy — see details in the Spaces article.
  • "Access restricted". A corporate space is visible to all organization members by default. To close it off to a specific person, grant them the "Access restricted" status — it overrides the default. Access can be restored with the "Restore access" button.
  • Assigning a Space Admin. Only the organization Owner or Admin can promote a member to Space Admin. A Space Admin cannot change the role of another Admin of the same space — this protects against mutual lockout.

#Related articles

  • Team Management — inviting people and changing organization roles
  • Spaces — creating spaces and managing their members
  • Activity log — who changed roles and access, and when