Team and organization

What an organization is

An organization is the account: it owns the plan, the payment method, every activated property, and the roster of people who can reach them. One is created for you at signup, named from your name, and if you work alone you can leave it alone entirely.

What is shared, and what is not

The line runs between the corpus and the questions you ask of it.

Shared by everybody

Every property anybody has activated, with its full record. Which of those are being watched, and so the property digest that follows from it. The plan and its monthly activation allowance. The map, search and every covered region.

Personal to each person

Watchers, and the daily digest each one produces. Your name, email and password.

That split is deliberate. A property is expensive to assemble and equally useful to everybody, so it is bought once, shared, and watched by the account rather than by one person. A watcher is a question about somebody's own job, and an estimator and a business developer working the same county want different ones. Nobody has to compete for slots, because the watcher cap is per person rather than pooled.

Inviting people

On the Team page, owners can invite by email address. The invitation arrives as a link.

• Somebody who already has a DeltaVisor account signs in to accept, and the membership is added to their existing account.
• Somebody new sets a name and a password on the invitation screen itself, and the account and membership are created together.

Invitations expire. The Team page shows the expiry date for each one, and an owner can revoke a pending invitation, which returns the seat immediately.

Owners and members

Two roles, and the difference is about acting rather than seeing.

Owner

Everything a member can do, plus: invite and revoke, change somebody's role, remove a member, rename the organization, and manage the plan and payment.

Member

The whole product: the map, search, activating properties, building watchers. They can see the roster, because knowing who your colleagues are is not a privilege, and they cannot change it.

There can be more than one owner, and promoting somebody is a dropdown on their row. An owner cannot demote themselves from the roster, because an organization cannot be left without one. Leaving is the deliberate way out, and it is on the settings page.

Seats

How many people can be on an account is set by the plan, and the counter is at the top of the Team page. Both members and pending invitations count against it.

At the cap, the invite control says so and points at the two ways forward: revoke a pending invitation, or move up a plan. Current seat numbers are on Billing.

Removing somebody

Owners can remove a member from their row. It asks first, and the effect is immediate.

What survives: everything the organization owns. Properties they activated stay, with their history, and the seat is freed. Their watchers are not deleted, though the digests stop, since a watcher is only delivered to somebody with access.

Renaming, and leaving

Both are on Organization settings. The page is deliberately small: the name, and the way out.

The name is what teammates see and what appears on invitations you send. Only an owner can change it.

Leaving ends your access to that organization and everything in it, immediately. It cannot be undone from your side; you would need a fresh invitation to come back. You cannot leave an organization where you are the only member, because that would strand the account and its plan. Invite somebody first, or cancel the subscription and stop using it.

Working with more than one organization

One account can hold memberships in several organizations, which happens when a consultant is invited into a client's account. Each has its own plan, its own properties and its own roster, and nothing crosses between them.