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

# Set up your workspace

> Build a small, useful starting point before inviting your team.

**Outcome:** one useful shared procedure, a clear access structure, and a
teammate who can find it.

**Before you start:** you need workspace Owner or Admin access for team
administration. New workspace owners first complete
[account and workspace setup](/getting-started/account). Team membership and
team vaults require a plan that supports them;
[check your plan](/administration/billing).

<Steps>
  <Step title="Choose one first use case">
    Start with a procedure people ask about repeatedly: client onboarding,
    meeting preparation, or a team handbook. Name one person responsible for
    keeping it accurate.
  </Step>

  <Step title="Choose the access boundary">
    Use Company for broadly shared knowledge. Use a team vault when membership
    needs to differ, and folders for topics with the same audience. Review
    [vault access](/collaboration/vault-access) before placing sensitive
    material.
  </Step>

  <Step title="Choose a starting structure">
    An empty vault can receive a [wiki template](/library/wiki). Apply it before
    adding files. If your vault already contains knowledge, organize it
    deliberately; do not delete existing content merely to apply a template.
  </Step>

  <Step title="Write one useful page">
    Follow [Build a company wiki](/tutorials/company-wiki). Include when to use
    the procedure, its owner, steps, and links to supporting sources. Verify the
    page appears in Search.
  </Step>

  <Step title="Invite and verify">
    [Invite your teammate](/collaboration/team), grant the required vault role,
    and send them [Join your team](/getting-started/join-team). Have them open
    the page using their own account. Your administrator view cannot prove their
    access.
  </Step>
</Steps>

## Check your result

Your teammate can find the procedure and knows whom to ask about it. If they
need to contribute, they can save a small agreed edit and you can inspect it in
**Activity**.

## Keep the rollout small

Expand after the first workflow is useful. Add department vaults when access
needs justify them. Use [Keep knowledge useful](/knowledge/maintenance) to
establish a review habit, and
[Employee onboarding](/tutorials/employee-onboarding) for later teammates.

**If it did not work:** review [editing access](/help/cannot-edit) or
[accounts and invitations](/getting-started/account).