Availability and seats
An invited member can join an active Professional or Enterprise workspace regardless of their personal plan. Workspace entitlement follows the organization owner’s subscription.
If the owner downgrades below Professional, existing workspace operations are blocked until the owner restores an eligible plan.
Shipped capabilities
Organization profile
Store a workspace name, website, description, and primary vertical for team identification and administration.
Membership
Invite members by email, track pending and active seats, and remove non-owner members.
Reviewer qualifications
Designate medical, legal, compliance, brand, or editorial reviewers independently from permission roles.
Deterministic review routing
Assign governed review obligations to active, qualified members and reroute pending work when qualifications change.
Review SLA overrides
Override how many hours a review role gets before an assignment counts as breached, per organization.
Vertical enablement
Restrict which verticals in the catalog members can generate against, enforced at the point of generation.
Organization profile
An organization Admin can create or update these fields:Name, website, primary vertical, and description are workspace metadata. They are not currently injected automatically into generation prompts, retrieval filters, or private corpora. Add required business context to the production brief or a personal style/corpus source when it must affect an output.Enabled verticals is the exception — it is enforced. Leaving every vertical checked (the default for a workspace that has never changed it) allows the full catalog; unchecking one blocks members from starting a generation against it, with a clear error rather than a silent substitution.
Membership roles
Workspace roles and reviewer qualifications solve different problems.
Editor and Viewer are currently membership classifications; they do not grant shared-library access or override permissions elsewhere in the application. The organization owner is always an Admin and cannot be removed or demoted by another Admin.
Invite a member
1
Enter the recipient email
Use the exact address the recipient will use to sign in. Email matching is case-insensitive, but the account address must otherwise match the invitation.
2
Choose a membership role
Select Admin, Editor, or Viewer. Reviewer qualifications are assigned separately after acceptance.
3
Send the invitation
WriterzRoom creates a single-use bearer token and delivers an acceptance link through the configured Resend account. The link expires after seven days.
4
Sign in and accept
The recipient opens the link and signs in with the invited address. The sign-in redirect preserves the invitation token, and successful acceptance changes the seat from Pending to Active.
An Admin can cancel a pending invitation by removing the pending member. An expired link is removed when used; the Admin can then issue a new invitation.
Reviewer qualifications
After a member accepts an invitation, an Admin can designate one or more qualifications:- Medical
- Legal
- Compliance
- Brand
- Editorial
Review SLA hours
Each review role carries a default SLA — how long an assignment has before it counts as breached — set by the vertical and tightened automatically when a claim needs substantiation. An Admin can override the default per role from Workspace → Team. Leaving a role blank keeps the platform default for that role and vertical. An override applies organization-wide for that role; it does not narrow further by vertical. Overriding timing never changes which reviews are required — that stays derived from the vertical and the quality gate’s findings, not configured.Your Credits
This tab reads the signed-in user’s personal credit ledger and shows:- Available credits
- Personal monthly allocation
- Credits used during the current month
Your Activity
This tab shows up to 50 recent activity records for the signed-in user. It does not aggregate other members, is not an organization-wide audit, and is not an append-only compliance record. Organization-wide audit reporting, retention controls, and export are not currently available.Operational requirements
Workspace invitations require:RESEND_API_KEY- A verified sender configured through
RESEND_FROM_EMAIL NEXTAUTH_URLorNEXT_PUBLIC_APP_URLset to the public application origin- The latest database migration, including
OrganizationMember.inviteExpiresAt
https://writerzroom.com, but staging and preview environments should always set their own explicit URL so invite links return to the correct deployment.
First-time setup
1
Create the organization
Add its identifying fields. Professional creates a five-seat workspace; Enterprise has no application-enforced seat cap.
2
Invite Admins and reviewers
Send invitations, wait for acceptance, and keep administrative access limited to people who manage the workspace.
3
Assign verified qualifications
Designate only competencies the organization has independently confirmed. WriterzRoom uses them for routing, not credential verification.
4
Process governed reviews
Use the Review Queue to approve, reject, and monitor assigned obligations before protected publication actions.
Related pages
Review Queue
Process assigned governed-review obligations and understand publication blocking.
Content Governance
Learn how policy, assurance, validity, and reviewer decisions are recorded.
Private Corpus and MCP
Understand private source isolation and the separate curated-corpus service.
Profile and Settings
Manage personal preferences, billing, API access, and security.