Roles & permissions

How Lumio uses roles to manage team access, integrations, and workspace settings.

Lumio uses three roles per organization: owner, admin, and member. Roles control who can change team membership, manage workspaces, and connect or push to integrations. Day-to-day work — scoring, enrichment review, browsing catalogs — is open to every role.

Owner

  • Full control of the organization
  • Invite, remove, and change the role of any other member
  • Update organization name and settings
  • Create, update, and delete workspaces
  • Connect, sync, and push to integrations (Shopify, Google Analytics)
  • Manage billing and plan changes
  • All product features (catalog, scoring, enrichment, schema health, analytics)

Every organization has exactly one owner.

Admin

  • Invite and remove team members (cannot change roles — only the owner can do that)
  • Update organization name and settings
  • Create, update, and delete workspaces
  • Connect, sync, and push to integrations
  • Manage billing and plan changes
  • All product features

Member

  • All product features — view catalogs, run scores, review enrichments, browse Schema Health and analytics
  • Voice rules: can create and manage rules in workspaces they belong to
  • Read-only on team and organization settings
  • Cannot connect or disconnect integrations, push to Shopify, sync from Shopify, or modify workspaces

Workspaces

Each workspace represents one store or site. Catalogs, scores, enrichments, integrations, and the brand profile are all scoped to a workspace. A workspace has one active catalog at a time — importing replaces it (the previous catalog is archived).

Organizations can run multiple workspaces — useful for brands operating multiple stores from one account. URLs reflect the active scope: /o/<organization>/w/<workspace>/....

A team member has the same role across every workspace in the organization. Per-workspace roles are not supported today.

Inviting team members

Owners and admins can invite new members from team settings. The invitee receives an email with a unique, expiring token. Accepting the invite adds the user to the organization with the assigned role.

Owners and admins can also revoke pending invites or resend them.

Sessions

Sessions expire after 7 days. Authentication uses email-and-password or Google OAuth, with email verification required on signup.