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 depending on role and configuration. |
| Snippets | Yes | They are shared as notes with a shortcut. |
| Links | Yes | Useful for standardizing internal shortcuts and searches. |
| Company variables | Yes | They are managed from the team settings. |
| Personal content | Not automatically | Your personal space remains separate from the shared one. |
Organization layers available in Teams
- 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 switch to frozen or read-only mode depending on the situation detected by the extension.
If a user is removed from the team, NexoPad can clean local data related to that organization and show a warning to prevent the person from continuing to work with information that no longer belongs to them.