Teams and Contexts

Everything you create in CredenShare belongs to exactly one context, and the context that was active when you created it decides where it is listed and who else can see it.

Personal and team contexts

A personal context is your own workspace. Shares, secure requests, pastes and field templates created there belong to you alone — nobody else can list them, including the owner of a team you belong to. Your own plan governs what you can do and how many shares you may create.

A team context is a workspace owned by one account and shared with the people it has invited. Items created there belong to the team rather than to you personally, and the team owner's plan — not yours — decides which features are available and which allowance the item draws on.

You are always in exactly one context. The list views call it your workspace and the My Teams page calls it your context; they are the same thing.

Switching context

The switcher is the button at the top of the left sidebar, directly beneath the logo. It shows the active context — Personal, or the team's name — with an up/down chevron. Open it and pick Personal or any team you belong to. A tick marks the active one.

The switcher appears only once you belong to at least one team. Until then everything is personal and there is nothing to switch.

Two other places change context:

• My Teams — every team card carries a Use Context button; the active team shows Active instead. While a team context is active the page also shows an Active context: banner with a Switch to Personal button.
• The top bar shows the active team's name beside the page title. In personal context it shows nothing.

Switching does not reload the page. The dashboard, Shares and Secure Requests refetch for the new context, and the plan behind your feature gates is re-resolved at the same moment. The sidebar's Templates link does not refetch — it changes destination, pointing at your personal templates in personal context and at the team's own templates page in a team context.

Where a new share lands

Whichever context is active when you press create is the context the item is created in. That applies to every creation surface: the Create Share modal, Quick Share on the dashboard, SecurePaste, and Create Secure Request.

The Create Share and Create Secure Request modals show a small badge in their header naming the context the item will land in — a person icon with Personal, or a building icon with the team name. SecurePaste and the dashboard's Quick Share show no such badge, so check the top bar before you create.

The Shares and Secure Requests pages carry a scope toggle above the table: This workspace / All workspaces. All workspaces merges personal and every team you belong to into a single list and adds a Workspace column naming each row's context. It is a reading view only — creation still follows the active context. On a large account it can show a capped subset per workspace and says so: "Showing a capped subset per workspace — refine with search to narrow results."

Who can see what

Inside a team, visibility depends on your role, and it is enforced on the server rather than in the interface.

A member cannot widen that from anywhere in the app. Nobody outside the team sees a team item at all.

Seeing a row is not the same as being able to open it. Shares created in the app are end-to-end encrypted on every plan and the key travels in the link, not in the record, so a colleague looking at your team share sees its title and its settings but cannot rebuild the link from the row. Copy link works for them only where zero-knowledge custody is in use (the zero_knowledge entitlement, Business and Enterprise), which stores a copy of the content key wrapped to the team — and only for a colleague who is enrolled in custody and has unlocked it. Without custody, the key exists only in the browser that created the share. A share created through the Slack app is the exception: it is encrypted on our servers, so its link carries no key and anyone who can see the row can copy a working one.

Dashboard tiles stay personal inside a team workspace. The page says so:

Showing your own activity in this workspace. The Shares list shows the whole team's items if you're an owner or admin.

What the active context changes

Field templates catch people out: the personal and team libraries are entirely separate. A template you saved personally is not offered while a team context is active, and a team template is not offered in personal context.

Branding is two separate settings for the same reason, both gated on the custom_branding entitlement (Business and Enterprise). The personal one is the Branding tab on your account page; each team has its own, reached from a Custom branding card on the team page and editable only by an owner or admin.

The top bar's emergency expire button — tooltip "Emergency: force-expire every personal share & request" — is deliberately personal in every context. Its confirmation reads: "Scope: personal shares + requests only. Team-scoped resources are managed by each team's owner."

The allowance follows the context

A share created in a team context counts against the team owner's allowance. A share created personally counts against your own. That holds whatever your role is.

For an owner the two are a single pool: their allowance covers their own personal shares plus every share created in every team they own. Adding a team does not add an allowance.

Expired and deleted shares still count, in either context. Removing a share frees nothing. See Plans and share allowance for the per-plan figures.

Nothing moves between contexts

There is no way to move a share, secure request, paste or field template from one context to another. A created share has no edit operation at all — it can only be created, read and expired. If something landed in the wrong place, create it again in the right context and expire the original, remembering that the original still counts against the allowance it was charged to.

Which plans include teams

Teams come from the multi_user entitlement.

Yearly plans match their monthly equivalents.

Being invited requires no plan of your own. A Free or Solo account can be a confirmed member of somebody else's team and gets the switcher, the My Teams page and the team's workspace with it. What it does not get is the owner side: no Create Team button and no Members entry in the sidebar, both of which are sold by the plan rather than granted by membership.

An account with neither a team plan nor a membership sees My Teams as an upgrade prompt headed Teams require a paid plan.

Next

• Members, roles and seats — inviting people, what each role can do, and how seats are counted and billed
• Joining a team — what to expect as an invitee
• Custom branding — branding the recipient view, per team
• Policy and audit — org-wide inactivity limits, IP restrictions and access trails