Skip to main content

Overview

ManaLens uses workspace roles to control what each teammate can see or change. A role applies to every project in the workspace.
  • Owner: full access. Can invite admins, transfer ownership and delete the workspace. Each workspace has one owner.
  • Admin: manages members, invitations, billing and project settings. Cannot invite admins or delete the workspace.
  • Editor: creates and changes dashboards, charts, segments and alerts, runs SQL and asks Ask AI questions. Cannot change members or key project settings.
  • Viewer: read-only access to projects and reports.

Permissions

Changes to members, billing, project settings and keys also need a session verified with MFA, even for owners and admins.

Invitations

Owners and admins invite people from Members in the workspace menu.
1

Open Members

Open the workspace menu and click Invite members.
2

Invite

Enter the email address and choose a role. Admins can invite editors and viewers only.
3

Accept

The user gets an email with an accept link. Only the invited email address can accept it.
An invitation is valid for seven days. You can resend or cancel a pending invitation, or change its role.

Change or remove a member

On Members, change a member’s role or remove the member. A member can also leave a workspace. The owner can make another member the owner with Transfer ownership. When a member leaves or is removed:
  • Their API keys with SQL or chart scopes stop working.
  • Their connected MCP apps lose access.
When a member’s role goes below editor, their API keys keep only the read scopes. See scopes.

Audit log

Owners and admins can open the Audit Log from the workspace menu. It lists who did what and when, such as invitations, role changes, key creation and rotation, SQL runs and alert changes. Filter by action and by time (last 24 hours, 7 days, 30 days or all time). The audit log never stores IP addresses, tokens, invitation links, webhook URLs, SQL text or Ask AI questions. Where it needs to identify one of these, it stores a hash. Changes made through the MCP server (with an API key or a connected MCP app) show via: mcp.