1Done: Explain how workspaces, teams, experiences and roles decide what each person sees and does.
2Done: Create roles that give each job only the access it needs.
3Done: Group people into teams, and into workspaces if you run more than one business.
4Done: Add colleagues with the right roles, in the right places, with the experiences they need.
5Done: Check what anyone can do, and switch off access the day someone leaves.
Steps you skipped
You did every step.You did every required step.
Optional, not done
1Skipped: Step 1 · How workspaces, teams and experiences control accessStage 1: Plan who sees what · Concept · 5 minBefore you give anyone access, know where they'll work and what they'll see. These three ideas decide both.Go back to step 1
2Skipped: Step 2 · How roles and permissions workStage 1: Plan who sees what · Concept · 8 minRoles are how you give access safely: once per job, not person by person. One rule matters most: access only ever adds up.Go back to step 2
3Skipped: Step 3 · Super admin vs AdministratorStage 1: Plan who sees what · Concept · 5 minA super admin skips every check. Giving it out "to save time" is the most common way access goes wrong.Go back to step 3
4Skipped: Step 4 · Create a role and assign permissionsStage 2: Set up roles and teams · Guide · 15 minStart each role from what the job must do. Leave everything else off: you can add a permission later, but a leak can't be undone.Go back to step 4
5To do: Step 5 · Add a workspace for another businessStage 2: Set up roles and teams · Guide · 10 minOpen step 5
6Skipped: Step 6 · Create a team and add membersStage 2: Set up roles and teams · Guide · 10 minTeams let you give a role to a group in one place, and share views and work with them.Go back to step 6
7Skipped: Step 7 · Create a userStage 3: Add your people · Guide · 10 minEach person gets their own sign-in, so every action is recorded against the right name. Never share an account.Go back to step 7
8Skipped: Step 8 · Give a role in one workspace or teamStage 3: Add your people · Guide · 10 minGive a role only where the job happens. A role given in one team applies only there.Go back to step 8
9Skipped: Step 9 · Choose which experiences a user can enterStage 3: Add your people · Guide · 5 minThe experience decides what the person's menu and home page look like. Give only the ones their job uses.Go back to step 9
10Skipped: Step 10 · See why someone can do somethingStage 4: Check and keep it tidy · Guide · 10 minCheck one person from each job. If something is there that shouldn't be, the panel tells you which role gave it.Go back to step 10
11To do: Step 11 · See Laramin as one of your colleaguesStage 4: Check and keep it tidy · Guide · 10 minOpen step 11
12Skipped: Step 12 · Switch off a leaver's accountStage 4: Check and keep it tidy · Guide · 5 minWhen someone leaves, switch their account off the same day. Their history stays; their access doesn't.Go back to step 12
How Laramin decides whether an IP address may sign in, how Blocked IPs and IP Rules relate, which rule wins, and what the policy mode, auto-block and break-glass settings change.
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Laramin Help CenterTutorial checklist
Bring your team in safely
Give every colleague their own sign-in and only the access their job needs. You'll plan who sees what, set up roles and teams, add people, check their access and switch off accounts when people leave.