Workspace Access and Permissions

How access to StretchDocs works

StretchDocs sits inside StretchSuite, so who can use it is governed by your organization membership, not by per-document sharing links. Three things determine access:

1. You are signed in to an organization. Every request is scoped to the organization you are working in. StretchDocs only ever shows that organization's documents.
2. Your role in that organization. Organization owners and admins automatically have access to every app, including Docs.
3. Your granted apps. Members who are not owners or admins are given access to specific apps individually. To use StretchDocs, a member must have the Docs app in their allowed apps.

If you are a member without the Docs app granted, StretchDocs returns a clear message — "You do not have access to this workspace app" — instead of showing documents.

Per-organization isolation

StretchDocs enforces strict tenant isolation. Documents belong to exactly one organization, and the organization is taken from your authenticated session — never from anything you type or send. That means:

• You can never see, edit, or export another organization's documents.
• Members of your organization with Docs access see the same shared library.
• Templates are the one shared resource. The starter templates (SOP, Product Spec, Meeting Notes, Client Handoff) are platform-maintained and available to everyone, but they contain no customer data.

Grant a teammate access

App access is managed in your organization's admin settings, not inside StretchDocs itself.

1. Open your Organization / Workspace settings and go to Members.
2. Find the member and open their access panel.
3. Confirm their role. Owners and admins already have Docs.
4. For a regular member, add Docs to their granted apps and save.
5. Ask the member to reload StretchSuite. Docs now appears in their launcher.

Owner vs. document owner

Two different "owner" ideas exist in the suite; don't confuse them:

• Organization owner/admin — a platform role that controls access to apps and settings.
• Document owner — a metadata field on each document naming the person accountable for that document's content. Anyone with Docs access can be set as a document owner, regardless of platform role.

A realistic example

An agency runs StretchSuite for its own team and for a client organization. The agency's admin adds a new junior writer as a member and grants them the Docs app so they can draft SOPs — but not the Billing app. The writer signs in, sees only the agency's document library, and drafts a procedure. When the agency later works inside the client's organization, the client's documents are a completely separate library; nothing crosses over.

Tips

• Grant Docs to anyone who writes or reviews — reviewers need access to leave comments and suggestions.
• Keep the number of owners/admins small; most people only need member access with specific apps.
• The document owner field is for accountability. Set it even for people who won't be admins.

Troubleshooting

"You do not have access to this workspace app." Your membership doesn't include Docs. Ask an owner or admin to grant it.

"You are not a member of the requested workspace." You're trying to reach documents in an organization you don't belong to. Switch to the correct organization.

"A workspace user is required" / access can't be verified. Your session is missing or expired. Sign out and back in; if it persists, your membership check may be temporarily unavailable — try again shortly.

I can see the app but not a specific document. Documents are org-scoped. If it was created in another organization, it won't appear here.