Browse articles

Control access to contacts

Choose whether staff are denied the shared directory or can inspect it without editing records.

What you'll achieve

Set and verify Hidden or View access to contacts.

You'll end up with: Marcus Webb has Viewer access and can inspect contacts without changing them.

The directory and project editing compose

Contacts controls contact records, contact types, and project associations. Hidden denies the Contacts route. View opens the directory without create or edit actions. Edit allows contact and contact-type changes.

Linking a contact to a project needs two permissions together: Contacts Edit and Tasks Edit on the admitted project branch. Contacts Edit alone cannot change a project the person cannot edit.

Build a clear Hidden case

None of the non-Admin built-in levels keeps Contacts Hidden, so the tutorial creates Contacts Hidden. New custom account levels begin with Contacts Hidden and Reports View.

  1. 1

    Create Contacts Hidden from Resources, Access Levels.

  2. 2

    Assign Contacts Hidden to Marcus Webb and click Save Changes.

  3. 3

    Start Preview and open Contacts to confirm the Access Restricted screen.

  4. 4

    Stop Preview, save Viewer, and preview again.

  5. 5

    Open Contacts and confirm the directory is visible while Add Contact is absent.

    Step 5

Troubleshooting

  • Contacts opens but Add Contact is missing. The person has View rather than Edit.
  • A contact cannot be linked to a project. Confirm Contacts Edit and project Tasks Edit.
  • A contact report is missing. Reports also applies the Contacts base-entity permission.

Where this fits next

Learn the working directory in contacts and clients, or revisit setting and previewing access.