Skip to main content
A workspace has one shared user directory for editors, internal app members, and public app users. Store extra details in your own tables and link them to the person with a User field.

​
What belongs where?

The directory appears in a dedicated users panel in the database. You cannot add columns to it. SSO attributes, when enabled, can also provide details about the signed-in person.
1

Open the relevant table

Use Profiles for personal details, or an existing table such as Requests or Orders for work belonging to someone.
2

Add a User field

Choose the User field type. Give it a clear name such as Owner, Assignee, or Submitted by.
3

Choose the field settings

Decide whether it holds one person or several, and whether to show only your team. Review User field settings, including what happens when a user is deleted.

​
Ask Zite for the behavior

  • Personal records: “Only show each person requests where they are the owner.”
  • Profile editing: “Let each user update their phone number in Profiles.”
  • Attribution: “Record who submits each request.”
  • New profiles: “After someone signs up, add a linked record for them in Profiles.”
The last example uses an After sign up rule. Test with two users to check that each sees only the intended records.

​
Access and data are different

  • Manage who can enter each app from Users, not from the database’s read-only directory.
  • Removing access to one app does not delete the person or all their records.
  • If the person is deleted from the shared directory, linked records remain by default. Delete row when user is deleted changes that behavior for the field.
Keep historical tasks and orders when a person leaves. Only enable automatic row deletion where removing the related record is intended, such as a disposable profile.
New apps do not need user sync to connect people and records.
Last modified on October 22, 2026