How the shared company workspace works
Teams adds a collaborative layer on top of notes, snippets, links, and variables so knowledge no longer lives scattered around.
In Teams you can work in a personal space and also in one or more shared spaces. That content can go through approvals, be restricted by department, and inherit organization-wide settings.
End-user documentation should explain this very clearly, because not everything you see in personal mode behaves the same way inside a company workspace.
What is usually shared in a team workspace
| Resource | Shared | Useful note |
|---|---|---|
| Notes | Yes | They can be subject to approval or read-only mode depending on role and team policy. |
| Snippets | Yes | They are shared as notes with a shortcut. |
| Links and groups | Yes | They help standardize access, internal searches, and working sessions. |
| Company variables | Yes | They are managed from the team settings and can feed shared snippets. |
| Personal content | Not automatically | Your personal vault remains separate from the shared vault even if you work in the same browser. |
Organization layers available in Teams
- Workspace selector to distinguish your private personal vault from the shared team vault.
- Departments to segment content.
- Strict isolation so each user sees only what belongs to them.
- Reusable company variables in snippets and templates.
- Team branding, primary color, logo, and visible workspace name inside the experience.
- Broadcast messages or announcements sent by the organization.
What happens if the company freezes or your membership changes
If the team subscription enters expired, unpaid, or canceled status, the experience can move into frozen or read-only mode. In practice that means you may still see shared content, but you will not necessarily be able to change it.
Role also matters: a viewer already lives in a more restricted experience, and an editor can see pending states where an admin sees approved content. A read-only label does not always mean something is broken; many times it is simply an accurate reflection of your permissions.
If a user is removed from the team, NexoPad can clean local data related to that organization and show a warning so the person does not keep working with information that no longer belongs to them.