Explanation

Who sees which entries

In a collection with an owner field, people see the entries they own plus the entries no one owns, unless their role allows seeing every entry. Collections without an owner field are visible in full to everyone who can open them. The table opens on your own entries by default, which is a view choice, not a limit.

In a collection with an owner field, people see the entries they own plus the entries no one owns, unless their role allows seeing every entry. Collections without an owner field are visible in full to everyone who can open them. The table opens on your own entries by default, which is a view choice, not a limit.

Requirements

None to read. To change who sees what: a role that can manage roles and edit the collection's fields.

The owner field

A people field can be marked as the one that says who runs an entry: the account manager on a company, the recruiter on a candidate. That field is what record-level visibility reads. A collection can have none, and then visibility is decided by the collection alone. See Fields: built-in and your own.

When you create an entry in such a collection, you are set as its owner unless you choose someone else. Entries from your website, imports, and integrations arrive with no owner.

Who sees which entries

PersonSees
A role allowed to see every entry, such as AdminEvery entry in the collection
Anyone else with access to the collectionEntries they own, plus entries with no owner

A recruitment agency with five recruiters gives each one the Recruiter role. Each sees their own candidates and the unassigned pool, and picks new candidates from the pool. The team lead's role allows seeing every entry, so the lead sees all five recruiters' candidates.

"Mine" is a view, not a wall

The table opens on your own entries. For someone who can see every entry, that is only a starting view: they can switch to all entries at any time. For everyone else, "mine and unowned" is also the limit of what they can see.

What follows the same rule

Notes and limitations

  • Assigning an owner to someone outside the business is refused. An entry owned by an outsider would be visible to no one.
  • An empty owner is a choice. Clearing the owner puts the entry back in the pool everyone can pick up.
  • Transferring a customer from the inbox changes the contact's owner, and with it who sees that contact.
  • Blueprint owner fields. On a protected owner field installed by a blueprint, the ownership setting cannot be switched off, because the whole collection would become visible to everyone.

For roles and permissions, see How access works and Design a role: what permissions govern.

Frequently asked questions

Why can't my team lead see all entries?
They see entries they own and unowned ones only. Give the team lead a role that can see every entry.
Who sees entries that come from the website?
They arrive without an owner, in the pool everyone with access can see.
What if my collection has no owner field?
Everyone who can open the collection sees all of its entries.