---
title: "Control who can access a Workspace - In Parallel help"
description: "Review Workspace members and shared audiences, then check depth, source visibility, expiry and access history."
url: https://www.in-parallel.com/help/control-workspace-access/
---

# Control who can access a Workspace

Review Workspace members and shared audiences, then check depth, source visibility, expiry and access history.

how to · admin

On this page

Workspaces & shared context

Start with two questions: **who belongs to the Workspace**, and **who receives context from it**. A person can receive shared context without becoming a Workspace member. Changing one audience’s share does not remove access they have through membership or another route.

## Before you start

Workspace Owners and Company Admins can manage sharing. Ordinary membership alone does not give that permission. If **Sharing** is unavailable, ask the Workspace Owner to review access with you.

The controls you can use depend on your permissions and the features enabled for your Company. A Company Admin’s ability to manage sharing does not, by itself, give them access to the Workspace’s content or its recipient preview.

## 1. Open the access overview

Open the Workspace and select **Share** in its header. In **Who has access**, review **Workspace members**, then open **Sharing** to review audiences.

Use **Manage members** for people who belong to the Workspace. See [Add members to your Workspace](https://www.in-parallel.com/help/add-members-stakeholders/) for the direct membership flow.

You may also encounter **General access** under **Settings → [Workspace] → Who is in**. Start with the Sharing grid when it is available; do not assume an older settings screenshot shows every current audience or control.

The General access choices include **Restricted — only people added**, **Anyone with the link**, and **Everyone at [Company]**. The first describes that general audience setting; it is not the same as marking the Workspace itself restricted. Likewise, **Discoverability** controls whether people can find the Workspace in directories, rather than granting access to its content.

## 2. Review each audience separately

Read the row label before changing anything:

| Audience | What to check |
| --- | --- |
| **Members of this workspace** | Membership access is managed separately. A company-wide depth limit does not narrow members’ access. |
| **Everyone at [Company]** | This is a company audience, rather than a list of direct Workspace members. |
| A named person | Check whether they already reach the Workspace through membership. A narrower share cannot override that membership. |
| Another Workspace | Check whether the row is editable, inherited or gives member-level access. Workspace-to-Workspace sharing may be unavailable for your Company. |
| **Anyone with the link** | Treat the address as shareable access. Check its depth and expiry before distributing it. |
| An agent | Check the named agent’s grant separately from your own connected AI assistant. |

Locked rows explain why their depth cannot be changed here. Follow **Manage members** or the named parent Workspace where appropriate. Do not interpret a disabled control as proof that the audience has no access.

## 3. Check depth and shared sections

The grid presents these depth choices where the audience supports them:

| Depth | Scope to review |
| --- | --- |
| **Nothing** | No context through this audience’s share. Other access routes can still apply. |
| **Where things stand** | Overview only. |
| **Updates** | Overview, strategy and pages, subject to each page’s own sharing setting. Confidential pages are not shared. |
| **Notes** | Extends to observations without source details. |
| **Everything** | Includes source details such as meeting summaries and transcript links, subject to the other applicable restrictions. |

Open the audience’s **Details** to inspect its sections and terms. Sections in this panel follow the depth; they are not individual section switches. **Custom** can mean a different section combination or shares with different expiry or sensitivity terms. Inspect the details before replacing it with a standard depth.

Share links support at most **Updates**. Restricting source details also does not mean that shared pages contain no information from meetings: a page can restate that information.

## 4. Review sensitivity, expiry and restrictions

Where a **Sensitivity** control is available, read its explanation alongside the depth:

- **Everything, sources named** retains named provenance for content the share can reach.
- **Confidential withheld, sources unnamed** and **Conclusions only** reduce what is shown. Pages are not shared at these reduced levels, and content without a usable rewritten version can be withheld.

These settings apply to the share. Membership or another, more permissive grant can give a person a broader view. Do not treat one row as a complete privacy check.

Check the actual expiry date for an active share. **No expiry** means there is no scheduled end for that share. Different underlying grants can end on different dates; inspect any mixed terms rather than assuming a single date covers them all.

If the Workspace is restricted, the Sharing screen warns that saved shares do not open its content while the restriction holds. Membership access is a separate route. Do not lift a Workspace restriction merely to test a share.

## 5. Check the recipient view

Where available, open **Details → See what they see**. Review each offered section. The preview shows the selected share’s reach; it is not an impersonation of a particular person’s complete account.

A person may also see meetings they attended. Inherited rows and locked membership rows do not offer the same preview controls. A Company Admin who does not also have member access cannot use the preview to read the Workspace.

Before relying on a sensitive sharing arrangement, have an intended recipient confirm what they can open using their own account. A visible dropdown or an owner’s view alone does not establish the recipient’s access.

## 6. Review agents and end access deliberately

A connected AI assistant acts within its user’s existing access and the scope of its connection. A separately named agent grant is another access route. Review its audience, depth and expiry; changing a human audience does not necessarily remove the agent’s grant. A depth limit can also hide the agent’s write-back instructions.

To change an editable audience, choose the intended depth or term and read the confirmation before selecting **Confirm**. Check the audience, sections, expiry and any other share the confirmation says will end. Company-wide sharing and share-link access can replace one another. Changing a share link’s depth can issue a new address and invalidate the old one.

To end an editable share, choose **Nothing** and review the confirmation. Then recheck the resulting row and any other routes that could still give the recipient access. Removing direct membership alone is not a complete revocation check.

Review **Recent changes** for changes made through the grid. Open **Access log** from **Who has access** to review recorded reads through shares. It is not a complete record of everyone who has read the Workspace: members opening their own Workspace are not logged there, and older records may lack the newer audience attribution.

## Related articles

- [Add members to your Workspace](https://www.in-parallel.com/help/add-members-stakeholders/)
- [Connect your AI tool](https://www.in-parallel.com/help/connect-your-ai-tool-mcp/)

[All help articles](https://www.in-parallel.com/help/)
