Team prompt management with roles and approvals
A HyperPrompt Team workspace gives a small team one shared set of prompts. Editors draft and revise, viewers read, and the owner approves. Every saved change is kept as a version, and activity is recorded.
Who it is for: small teams (the plan covers 3 to 25 seats) who use the same prompts and want one reviewed version instead of copies scattered across chats and documents.
Team plan limits
- $29/month, or $290 billed yearly, with 3 seats included. The owner counts as one seat.
- Extra seats cost $9/month or $90/year each, up to 25 seats in total.
- One shared workspace per Team plan.
- Active members and pending invitations together can never go over the number of seats you paid for.
- The plan includes everything in Pro, such as prompt versions, multi-model evaluations, API keys, and JSON export.
A three-seat workflow, step by step
Example setup: one owner, one editor, and one viewer, which uses all three included seats.
- 1
The owner buys Team and creates the workspace
The Team plan includes 3 seats, and the owner uses one of them. After subscribing, the owner names the workspace. Each Team plan includes one workspace.
- 2
The owner invites an editor and a viewer
Invitations go out by email with a role of editor or viewer. Each link expires after 7 days, and the person has to accept it while signed in with the invited email address. Pending invitations count toward your seats. With the owner plus two invitations, all 3 seats are in use and HyperPrompt rejects further invitations until a seat frees up. Invited people do not need a paid plan of their own.
- 3
The editor drafts a shared prompt
The editor creates a prompt in the workspace or moves a personal prompt into it from the prompt editor's Workspace menu. It starts as Draft. Each save creates a new version. When the prompt is ready, the editor sets it to Ready for review.
- 4
The owner reviews and approves
The owner can check the version history, compare an older version with the current text, and set the prompt to Approved. Only the owner can approve.
- 5
Changes go back to review
If someone edits the title or text of an approved prompt, or restores an older version of it, the prompt returns to In review until the owner approves it again.
- 6
Everyone can see what happened
The workspace activity feed records members joining and prompts being created, updated, approved, or commented on. Other members also get an in-app notification. The viewer can read the prompts and their history but cannot save changes.
What each role can do
| Action | Owner | Editor | Viewer |
|---|---|---|---|
| Read workspace prompts and their version history | Yes | Yes | Yes |
| Create, edit, and restore workspace prompts | Yes | Yes | No |
| Set a prompt to Draft or Ready for review | Yes | Yes | No |
| Approve a prompt | Yes | No | No |
| Invite members, change roles, remove members | Yes | No | No |
| Rename, delete, or transfer the workspace | Yes | No | No |
| Leave the workspace | Transfer or delete first | Yes | Yes |
These permissions are enforced by the server-side API, not only hidden in the interface. The owner can switch a member between editor and viewer at any time. When a member is removed, the prompts they wrote stay in the workspace.
What is shared and what stays private
| Workspace prompts and their versions | Shared with all workspace members. These prompts can't be made public. |
|---|---|
| Workspace activity feed | Shared with all workspace members. The feed shows the 50 most recent events. |
| Personal prompts and folders | Private to you, unless you publish a prompt or move it into the workspace. |
| Rules, skills, and MCP configs | Personal. They can't be added to a workspace. |
| Evaluation suites, enhancement history, context snippets, API keys | Personal to each account. |
Current limitations
- Each Team plan includes one workspace and up to 25 seats.
- Only prompts can be shared. Rules, skills, MCP configs, and evaluation suites stay personal.
- Comments on workspace prompts are stored and appear in the activity feed and notifications, but they can only be posted through the comments API for now. The in-app prompt editor doesn't show a comment thread yet.
- Approval has one step, and only the owner can approve. You can't require several reviewers.
- There is no SSO, SAML, SCIM, or automatic joining by email domain. Members are invited one at a time by email.
- There is no separate audit-log export. The activity feed shows the 50 most recent events.
- Deleting the workspace permanently deletes its prompts and their discussions. The owner has to type the workspace name to confirm.
- Ownership can only be transferred to a member who has their own Team plan, doesn't already own a workspace, and has enough seats for the current members and pending invitations.
Related
Bring your team's prompts into one reviewed place
Choose Team and set the number of seats on the pricing page, then create your workspace and send invitations.