Docsroom

Features / Permissions

Who sees which request packs, decided per person.

Not everybody on your team should see every request pack. A new colleague starts with access to nothing, and you give them what they need: the whole organisation, or a named list.

Team · role and reach
  • LSLaura Shawevery packAdmin
  • DCDev Chandra14 packsStaff
  • EBErin Boyle6 packsRead only
The model

The whole model, in one place

The owner is protected. Everyone else has a role, and a reach. Selected can be every request pack for a business or person, including ones added later, or a single pack.

  • A new invitation starts with nothing
  • Changing role and reach is one action, logged
Team · role and reach6 people
  • LSLaura ShawOwner, cannot be removedAll request packsAll
  • DCDev ChandraAdmin, runs the settingsAll request packsAll
  • ABAna BellTeam memberSelected request packsSelected
  • TRTom ReidTeam memberOnly allocated requestsAllocated
  • EBErin BoyleViewer, reads onlySelected request packsSelected
  • SCSam ColeTeam member, invited todayNothing yetSelected request packsSelected
Every change to a role or reach is a line on the trail.

An illustration. The names are made up.

Least privilege by default

Invite a colleague, a temp or a subcontractor and they can reach nothing until you say otherwise. That is the safe way round, and it takes one more click than the unsafe way.

A viewer really is read only

Not a member with the buttons hidden. The refusal happens on the server, so it holds however the request arrives.

Every change is on the record

Who changed whose access, and when. It is one line on the activity trail like everything else.

The pictures are illustrations. The names are made up.

Evidence

Proved, not asserted

The rules are checked against the running deployment before every release: an admin, a colleague across the whole organisation, a colleague given the request packs for one business, and a viewer, each doing what they should and being refused what they should not.

  • Given one business’s packs, refused another’s
  • A viewer cannot create or rename anything
  • The team list stays with admins
  • Signed out, the interface answers nothing at all
Who can see Ardley Foods · per pack
  • LSLaura ShawownerCan edit
  • DCDev ChandraCan edit
  • EBErin Boylecannot sendRead only

Two-factor when you want it

An authenticator app, recovery codes, and an admin who can lift it off a colleague who is locked out. A password reset never sidesteps it.

Two-factor · on your own sign-in
  • Authenticator appadded 12 AugustOn
  • Recovery codes8, shown onceNew recovery codes
  • Signed inthis laptop and a phone2 places

Read next

SecurityThe rest of the pictureTeam and sign-inThe help articleAudit and exportsWhat is recorded

Invite a colleague and try it.

Free for 14 days, no card.

Start freeBook a walkthrough