Team
A team gives further people access to the account without sharing credentials. Each person signs in with their own access and confirms with their own two factor authentication.
Where to find it
Section titled “Where to find it”Account → Team, direct address: dash.regfish.com/my/setting/team
Inviting
Section titled “Inviting”Under invite member you enter the email address. Two limits are stated there:
- 5 seats, the counter shows how many are taken.
- 7 days validity for the invitation. Once it expires it has to be sent again.
What roles do
Section titled “What roles do”Roles limit which areas a member may change at all. They are the coarse layer: without access to an area, no action shows up there either.
What protection rules add
Section titled “What protection rules add”Here is the connection worth knowing: protected actions apply to members too. The protection rules from the domain guardian do not disappear because somebody works through a team. Each member confirms a protected action with their own 2FA, not yours.
On top of that there is the four eyes mode: a protected action then also needs approval from a second person. That is the answer to a single member account being taken over, because a second factor alone does not help against that.
So the three layers interlock: the role decides whether somebody may do something, the protection rule what they confirm it with, and four eyes mode who else has to agree.