Trang này chưa có bằng ngôn ngữ của bạn. Bạn đang đọc bản tiếng Anh.
Glossary
Team workspace
A team workspace is one paid account that several people sign into separately, each with a seat and a rank.
What a workspace holds
Everything bought sits under one owner: the profile allowance, the machine seats, the shared address library and the folders.
A colleague joins that space instead of receiving a copy of it. Access ends in one step, on the day it should.
How a seat is taken
- 1
The person registers first
An invite is written to an address that already has an account, because owning an address is not something a server can prove.
- 2
The owner writes the invite
It names that one address, carries a code, expires after a week and can be withdrawn before anyone uses it.
- 3
The seat is counted twice
Once when the invite is written and again when it is accepted, under a hold on the owner's record so two people cannot take one seat.
What a colleague can reach
A rank says what a person may change. Folders say which profiles they see at all.
Profiles opened to them
Sharing hands over the profile itself, not the password of the account inside it.
Folders opened to them
An empty choice means no narrowing. One folder chosen means that folder and nothing else, including profiles kept outside any folder.
The shared address library
Anyone can work through an address already set on a profile. Editing the library, rotating an address or pulling the whole pool to a second machine belongs to a manager.
One profile in one window
A profile open on one machine is held there, and the second machine is told who has it instead of opening a second window.
That hold is what stops two colleagues from working one account from two places in the same hour.
When someone leaves
Being removed and walking out run the same path, so both end with the space in the same state.
Access closes with the seat
Their access to colleagues' profiles closes, and so do the shares on the profiles that leave with them. Profiles that stay with the owner keep the colleagues already working them.
The seat comes back
Machines they registered give their seats back, and an invite still waiting on their address is put out.
Paid work stays paid for
Profiles made inside the workspace stay with the owner, and what the person brought in leaves with them.
The trail stays
Their rows remain in the owner's history, and that history is read exactly then.
Often confused with
A shared login
One address and one password for everyone leaves no way to tell two people apart and no way to take access from one of them.
A plan named for teams
Seats are a line on the paid plans rather than a plan of their own, and the owner occupies one of them.
A folder
A folder narrows what a person sees inside the space. The space is the thing they are inside of.
What this does not do
- It does not sign a company in through one directory. Each person registers themselves first, and the invite is written to that address.
- It does not hand the address library to everyone on a second machine. Pulling the whole pool with its passwords needs a manager or higher.
- It does not wipe a colleague's machine. Taking a profile back removes it from their app and leaves the cookies already written to their disk.
- It does not make a platform allow shared work. Many of them forbid one account being worked by several people, and nothing here changes their rules.
Check it
Every line above comes from a file you can open.
- Seats are counted when an invite is written and again when it is accepted
- apps/server/src/team/team.service.ts · apps/server/test/team-money-seats.js
- An opened folder narrows the list and the direct open alike
- apps/server/test/group-access.js
- One window holds a profile and the second is told who has it
- apps/server/test/profile-lock.js
- Seats belong to the paid plans and the owner takes one of them
- packages/shared/src/index.js
Questions
- Does a teammate need their own subscription?
- No. The space belongs to the owner, and profiles made inside it count against the owner's allowance.
- Can two people open one profile at once?
- No. The second machine is told who holds it and can take it over on purpose, which is different from taking it by accident.
- Is the invite code enough on its own?
- No. It is written to one address that already has an account, it expires, and it can be withdrawn while it is still unused.
- Can I keep a contractor on one client?
- Yes. Put that client's profiles in a folder and open only that folder; the rule is read when profiles are listed and again when one is opened by identifier.
- What happens to the work after someone goes?
- Profiles the workspace paid for stay with the owner, and the record of what was done stays readable to the owner.
Put the team in one space
Invite a colleague into your own account, leave the profiles where they are, and take the access back in one step.