> ## Documentation Index
> Fetch the complete documentation index at: https://docs.writerzroom.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace

> Manage your organization profile, team members, credit pool, and activity log. Enterprise plan required.

The Workspace page is the B2B control surface for Enterprise accounts. It operates independently from personal Settings and applies configuration at the organization level, affecting every team member and every generation they run.

Navigate to **Workspace** in the left sidebar to access it.

<Note>
  Workspace is an Enterprise-only feature. Starter and Professional accounts see an upgrade prompt when navigating to `/workspace`. To upgrade, go to **Settings → Billing** or visit [writerzroom.com/pricing](https://writerzroom.com/pricing).
</Note>

## What Workspace Controls

<div style={{ display: 'grid', gridTemplateColumns: 'repeat(4, 1fr)', gap: '12px', margin: '1.5rem 0' }}>
  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '16px', background: 'rgba(255,255,255,0.04)' }}>
    <div style={{ fontWeight: 800 }}>Organization</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)' }}>Company identity and description injected into every team generation as persistent context.</div>
  </div>

  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '16px', background: 'rgba(255,255,255,0.04)' }}>
    <div style={{ fontWeight: 800 }}>Team</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)' }}>Member invites, role assignments, and access control across the workspace.</div>
  </div>

  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '16px', background: 'rgba(255,255,255,0.04)' }}>
    <div style={{ fontWeight: 800 }}>Credit Pool</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)' }}>Shared credit balance, monthly allocation, and per-member usage breakdown.</div>
  </div>

  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '16px', background: 'rgba(255,255,255,0.04)' }}>
    <div style={{ fontWeight: 800 }}>Audit Log</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)' }}>Chronological feed of team activity: generations, publishes, and member changes.</div>
  </div>
</div>

## Organization

The Organization tab is where you configure what WriterzRoom knows about your company. This information is not a preference — it is injected as persistent context into every generation any team member runs, without them having to re-enter it.

| Field                     | Purpose                                                                                                             |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Organization Name         | Identifies the workspace and appears in audit records                                                               |
| Website                   | Your company's primary URL, used as context for research and source filtering                                       |
| Primary Industry Vertical | Biases the RAG retrieval pipeline toward your domain during the research phase of every generation                  |
| Organization Description  | A concise summary of what your company does and who it serves — injected into every generation as grounding context |

### Writing an Effective Description

The Organization Description is the most impactful field in this tab. It replaces the need for each team member to explain organizational context in their generation inputs.

Keep it under 500 characters. Focus on: what your company does, the audience it serves, and any content positioning constraints that should apply consistently.

**Example:**

> Acme Health is a B2B digital health platform serving hospital systems and clinical research organizations. We communicate to healthcare executives, clinical informatics leads, and compliance officers. Content should reflect evidence-based standards and regulatory awareness.

A description like this ensures every generation — regardless of which team member runs it — starts with the correct organizational framing.

### Saving Organization Changes

Changes to the Organization tab save immediately on clicking **Save Changes**. The update takes effect on the next generation any team member submits.

## Team

The Team tab manages who has access to your workspace and what they can do inside it.

### Roles

<CardGroup cols={3}>
  <Card title="Admin" icon="crown">
    Full access. Invite and remove members, manage org configuration, and access billing. The organization owner is always an Admin and cannot be removed.
  </Card>

  <Card title="Editor" icon="pencil">
    Generate, edit, and publish content. Can access all workspace content, templates, style profiles, and publishing connections.
  </Card>

  <Card title="Viewer" icon="eye">
    Read-only access to the Content Library. Cannot generate, edit, or publish. Suited for stakeholders who need to review drafts without acting on them.
  </Card>
</CardGroup>

### Inviting Members

<Steps>
  <Step title="Enter the email address">
    Type the email address of the person you want to invite. The invitation is tied to that email — if they sign up with a different address, access will not apply.
  </Step>

  <Step title="Select a role">
    Choose Admin, Editor, or Viewer. You can change this after they accept.
  </Step>

  <Step title="Send the invite">
    Click **Send Invite**. The recipient receives an email with an acceptance link. Their status shows as **Pending** until they accept.
  </Step>

  <Step title="Confirm acceptance">
    Once accepted, their status changes to **Active** and they appear in the member list with their assigned role.
  </Step>
</Steps>

<Info>
  Pending invites are visible in the member list and can be cancelled by removing them before acceptance.
</Info>

### Removing Members

Click the remove icon next to any non-Admin member. Access is revoked immediately. Content the member previously generated remains in the library and is not deleted.

<Warning>
  You cannot remove yourself as the organization owner. To transfer ownership, contact [support@writerzroom.com](mailto:support@writerzroom.com).
</Warning>

### Role Changes

Role changes take effect immediately. Downgrading an Editor to Viewer removes their ability to generate or edit content starting with their next session.

## Credit Pool

The Credit Pool tab shows how your organization's credits are allocated and consumed.

| Metric             | Description                                                             |
| ------------------ | ----------------------------------------------------------------------- |
| Available Credits  | Current org-level balance available for generation                      |
| Monthly Allocation | Credits provisioned each billing cycle by the Enterprise plan           |
| Used This Cycle    | Total credits consumed by all team members since the last billing reset |
| Per-Member Usage   | Breakdown of credit consumption per active member this cycle            |

### How Credits Work for Teams

On Enterprise, credits are provisioned to the organization, not to individual accounts. Any team member drawing on the pool reduces the shared balance. The Credit Pool tab gives Admins visibility into how the balance is being consumed without requiring them to generate anything themselves.

Per-member credit caps are in active development. Contact [support@writerzroom.com](mailto:support@writerzroom.com) to discuss custom Enterprise credit arrangements in the interim.

<Info>
  Credit pack purchases made by individual team members on Enterprise apply to the shared org pool, not to a personal balance.
</Info>

## Audit Log

The Audit Log tab shows a chronological feed of team activity across the workspace.

Each entry records:

* **Who** — the team member who performed the action
* **What** — the action type (generation, publish, member invite, role change)
* **When** — timestamp of the event
* **Context** — the template used or content affected, where applicable

The log is append-only. Entries cannot be modified or deleted. This makes it suitable for internal review, stakeholder accountability, and content governance workflows.

<div style={{ border: '1px solid rgba(79,110,247,0.2)', borderRadius: '10px', padding: '20px 24px', background: 'rgba(79,110,247,0.04)', margin: '1.5rem 0' }}>
  <div style={{ fontSize: '11px', color: 'var(--colors-content-secondary)', textTransform: 'uppercase', letterSpacing: '0.06em', marginBottom: '14px' }}>Example audit entries</div>

  <div style={{ display: 'grid', gridTemplateColumns: '140px 1fr 140px', gap: '8px 16px', fontSize: '13px' }}>
    <div style={{ color: 'var(--colors-content-secondary)', fontWeight: '500' }}>Member</div>
    <div style={{ color: 'var(--colors-content-secondary)', fontWeight: '500' }}>Action</div>
    <div style={{ color: 'var(--colors-content-secondary)', fontWeight: '500' }}>Time</div>
    <div>Sarah Chen</div><div>Generated · White Paper · Healthcare</div><div>Jun 2, 9:14 AM</div>
    <div>Marcus Webb</div><div>Published · Dev.to · API Documentation</div><div>Jun 2, 11:32 AM</div>
    <div>Admin</div><div>Invited · [editor@acme.com](mailto:editor@acme.com) · Editor</div><div>Jun 2, 2:05 PM</div>
    <div>Jordan Lee</div><div>Generated · Blog Article · SaaS Tech</div><div>Jun 3, 8:47 AM</div>
  </div>
</div>

Full org-scoped audit logs covering all member actions, template usage, publish events, and billing changes are available on Enterprise.

## Enterprise Gate

Non-Enterprise accounts navigating to `/workspace` see a full-screen upgrade prompt that lists all Workspace capabilities and links directly to **Settings → Billing**.

| Plan         | Workspace Access |
| ------------ | ---------------- |
| Demo         | Upgrade prompt   |
| Starter      | Upgrade prompt   |
| Professional | Upgrade prompt   |
| Enterprise   | Full access      |

## Setting Up for the First Time

<Steps>
  <Step title="Complete the Organization profile">
    Fill in your company name, website, primary vertical, and description. This is the most impactful step — it improves every generation your team runs from day one.
  </Step>

  <Step title="Invite your team">
    Add team members by email and assign roles. Start with Admins and Editors. Add Viewers for stakeholders who need review access.
  </Step>

  <Step title="Review the Credit Pool">
    Check your current balance and monthly allocation. Share this with whoever manages content volume decisions for your team.
  </Step>

  <Step title="Monitor the Audit Log">
    After your first week of team activity, review the Audit Log to confirm usage patterns match expectations. Use it to identify who is generating most actively and which templates are in heaviest rotation.
  </Step>
</Steps>

## Related Pages

<CardGroup cols={2}>
  <Card title="Profile and Settings" icon="settings" href="/product/profile-and-settings">
    Individual account preferences, notifications, appearance, API access, billing, and security.
  </Card>

  <Card title="Brand Voice" icon="fingerprint" href="/product/brand-voice">
    Analyze writing samples to create reusable voice fingerprints applied during generation.
  </Card>

  <Card title="Verticals" icon="building-2" href="/product/verticals">
    How domain verticals govern templates, research behavior, and output quality.
  </Card>

  <Card title="Publishing" icon="send" href="/product/publishing">
    Connect platforms and publish finalized content directly from WriterzRoom.
  </Card>
</CardGroup>