Skip to content
Felspar
Esc
↑↓navigate↵open⌘Jpreview
On this page

Roles and permissions

Workspaces, owners, approvers, members and agents, what each can do, and how people join.

Workspaces

A workspace is one company’s space in Felspar. Its sources, packs, releases, agents and decisions are visible only inside it. Everyone in a workspace signs in with their own account.

Roles

Role Who Can
Owner The first person in the workspace Everything an approver can, plus change roles. The default accountable owner of every job.
Approver Members the owner promotes Everything a member can, plus approve and release packs, invite people, and register, change and revoke agents
Member Everyone else who joins Add sources, draft and propose packs, backtest, run decisions, inspect decisions and verify receipts
Agent A registered company agent, with its own key Read briefs and run decisions for its own jobs, and verify its own receipts. Nothing else.

Make more than one approver, so there is a backup. Only the owner changes roles, and the owner’s own role can’t be removed. Nobody is promoted to owner automatically.

What each action needs

Action Member Approver Owner Agent Through MCP sign-in
Add a source from a connected Doc Yes Yes Yes No Only via add_current_version
Read sources and proposals Yes Yes Yes No Yes
Check, propose, backtest Yes Yes Yes No Yes
Approve, release No Yes Yes No Never
Register, change or revoke agents No Yes Yes No Never
Invite people No Yes Yes No Never
Change roles No No Yes No Never
Run decisions Yes Yes Yes Own jobs only No
Verify receipts Any in workspace Any Any Own decisions only No

Through MCP sign-in means a person using Felspar from ChatGPT, Claude or another MCP client. That sign-in is deliberately narrower than the web app: it can read, draft, propose and backtest, and it can add a source only by reading a connected Doc’s current version with your own connection, never from text the assistant writes. Consequential actions stay on the web app, as your own click.

Document access is separate from roles. Reading, proposing from, backtesting, approving and releasing a pack built on a connected Doc also need your own current access to that Doc. See Connect Google Docs.

Joining a workspace

Felspar is invitation-only for now.

  • Invitations: the owner or an approver invites colleagues by email from Workspace → People and roles. The colleague gets an email and joins as a member.
  • Request access: someone without a workspace who signs in sees a short form (name, work email, optional company, what they want to use Felspar for). The request goes to the Felspar team; it grants nothing by itself.
  • Approved company domains: Felspar can tie a workspace to your company’s email domain for a pilot, so colleagues with a verified address at that domain join automatically. Ask the Felspar team.

Someone in several workspaces enters the one their sign-in went through, such as an invitation just accepted.

Sessions

You stay signed in on the same browser for up to 30 days, as long as your sign-in stays valid. Every request still checks your current membership and role, so removing someone or changing their role takes effect on their next request. Sign out ends your session and returns you to felspar.ai.

Removing access

  • People: removing someone from the workspace, or removing a role, ends that access on their next request. A removed role is never restored automatically.
  • Agents: Revoke this agent refuses its very next call. See Register an agent.

Was this page helpful?