LaunchPad Administration is the org-level control surface that sits above any individual agent. While Launch Pad is scoped to a single agent, LaunchPad Admin is where Org Owners and Admins manage the entire raia workspace — the people who can log in, the agents that exist under the org, cross-agent conversation history, immutable audit logs, and the resource and billing envelope that every agent runs inside.
In this section
- Invite teammates and external collaborators, and assign the right Org-level role.
- Enforce MFA and password policy across the whole workspace in one place.
- Audit and export conversation history across every agent for compliance reviews.
- Read the Activity Log to trace who changed what, when, and from where.
- Track token, storage, message, and per-skill usage against monthly billing limits.
- Set org-wide defaults for model, branding, data retention, and geographic access.
What's inside
- 01
Users
Invite users by email, assign an Org role (Owner, Admin, or Member), and grant per-agent access. Pending invitations, MFA enrollment status, and last-login timestamps are all visible here. Owners can also suspend or remove users without deleting their conversation history.
- 02
Agents
The org-wide list of every agent that exists in the workspace — including drafts, active, and archived agents. Owners can transfer ownership between users, clone an agent as a starting template, or archive agents that are no longer in use.
- 03
Conversations
A cross-agent search across every message the org has ever handled. Filter by agent, channel, date range, user, or Auditor flag, then export to CSV for legal, compliance, or QA review.
- 04
Activity Logs
Immutable, append-only log of every configuration change, key rotation, invitation, permission change, and login event across the org. Each entry includes the actor, timestamp, IP, and a diff of what changed — the primary evidence source for security audits.
- 05
Resource Usage
Live dashboards for tokens, messages, voice minutes, storage, and per-skill usage — rolled up across every agent in the org. Compare the current billing cycle against the org's monthly limits and see which agents are consuming the most.
- 06
Billing & Limits
Plan tier, seat count, monthly token / message / voice caps, and invoice history. Owners can raise or lower per-agent caps here so a single misbehaving agent can't consume the entire org's budget.
- 07
Settings
Org name, logo, brand color, default model, default language, data retention window, geographic allow/deny lists, MFA enforcement policy, SSO / SAML configuration, and API key management.
At a glance
| Org role | What they can do | Best for |
|---|---|---|
| Org Owner | Full control: billing, SSO, MFA policy, user management, and access to every agent. Can transfer ownership and delete the org. | Founders, account owner of record |
| Org Admin | Everything an Owner can do except billing and org deletion — invite users, manage agents, rotate keys, read all logs. | IT / platform team, security lead |
| Member | Access is scoped to the specific agents they've been added to. Can view conversations and reports for those agents only. | Functional experts, agent builders |
| External / Invited | Time-boxed access for contractors or partners. MFA is always required and access can be revoked with one click. | Agencies, auditors, temporary collaborators |
Tip
Turn on MFA enforcement in Settings before you invite the first external user. Once it's enforced org-wide, every new invitee is required to enroll during their first login — you never have to chase people to secure their account.