Teams

Who it is for

Research cells, policy desks and analysis teams of two or more who already work the way Vigil Professional works: over reviewed records, standing questions and stated evidence. Each member keeps an ordinary Vigil account and a private personal workspace; the organisation adds a shared one beside it.

What Shared Workspaces enable

• Shared collections. Working sets of canonical records — Watch questions, observables, developments, Tempo series — kept by the organisation, ordered and annotated, every reference provenanced to the record it names.
• The shared Brief Builder. One analyst drafts, another continues. Every save is a recorded revision with its author; a save that crosses somebody else's is caught and reported, never silently merged; any revision can be restored. Export — Markdown, print, JSON, evidence pack — is the same pipeline as a personal brief.
• Shared saved research. Saved queries, comparisons, timelines and monitor views move between a member's workspace and the organisation's by one explicit action, in either direction.
• One coverage. The organisation's subscription covers its members: the same module coverage, the full Professional toolset, for everyone in it.

How organisational access works

An owner founds the organisation from their Professional subscription and invites members by email — each invitation expires in seven days and must be accepted by the invited address. Three roles: the owner runs membership and billing, editors create and change shared research, viewers read it and work over the organisation's coverage. Removing a member ends their shared access at once; it never touches their personal account or workspace.

Nothing is shared by default. Membership never exposes anybody's personal collections, drafts, follows or notes; sharing is a deliberate move of one named item.

How it differs from individual Professional

Nothing is taken away and nothing is duplicated. The research corpus stays canonical and single; the tools are the same instruments in the same workspace. What Teams adds is the organisational layer: shared ownership of working material, provenance inside the team (who made it, who last changed it, what its history is), and one subscription answering for everyone's coverage.

Individual Professional continues unchanged — coverage and pricing are here.

Working in a shared workspace, step by step

1. The organisation is founded by its owner — any active Professional subscriber, from their account page. The owner designates their subscription as the organisation's coverage; every organisation starts with two seats, and seats bound how many may join.
2. Members are invited by email from the owner's account page. An invitation is personal, expires after seven days, can be revoked, and must be accepted by the invited address; accepting needs only an ordinary Vigil account.
3. The workspace context is explicit. The Library shows a workspace line — My Workspace and each organisation — and the address bar carries the context, so a save can never land in a scope you cannot see. My Vigil, follows and notes stay personal.
4. Sharing is one deliberate action. "Share to organisation" moves a saved query, collection, comparison, timeline or draft into the shared workspace; "To my workspace" moves it back. Nothing is shared by joining.
5. Shared drafts are sequential, with history. Every save records a revision with its author; a save that crosses somebody else's is refused with their name, never silently merged; any revision can be restored, as a new revision. Export — Markdown, print, JSON, evidence pack — is the personal pipeline, unchanged.
6. Membership is managed on the account page: roles (owner · editor · viewer), removal (immediate), invitations, seats, and ownership transfer to another member. Leaving or removal never touches anyone's personal account or workspace.

Data ownership and privacy. Shared items belong to the organisation and name their authors; personal items belong to the person and are invisible to the organisation. Deleting a personal account leaves the organisation's shared work in place, attributed to a departed author. If the organisation's subscription ends, the shared workspace closes but nothing in it is deleted — it reopens when coverage returns. Shared work references Vigil's research records and can never change them.

Starting a team

Any active Professional subscriber can found an organisation from their account page: name it, designate your subscription as its coverage, and invite your members by email. Two seats are included — you and one colleague, working over your coverage at no extra cost.

For a larger team, write to [email protected] with its size and the coverage you work on: seats beyond the included two and organisational pricing are settled per team.

Already in an organisation? It is managed from your account.