Site · Permissions
Site permissions overview
Last updated 18 November 2026
Profiles add fields to kinds of contact; access is controlled with authorization policies.
The Permissions module manages profiles. A profile is a set of extra fields for a kind of contact, such as Member or Supplier. You create the profile, define its fields, and assign it to CRM contacts, who then hold those fields. Profiles hold data only. They do not decide who can see what.
Where to find profiles
In the admin, open Permissions and choose Profiles. Open a profile to see its contacts, details, fields and event stream.
| Tab | What it shows |
|---|---|
| Contacts | The contacts that hold this profile. You can remove one, or all |
| Details | The profile name and its file |
| Fields | The fields the profile adds |
| Event Stream | What changed on this profile |
Access is set elsewhere
To limit who can open a page or call an endpoint, use an authorization policy. A policy can check whether a signed-in person holds a profile. The profile marks who is a member, and the policy admits members.
Example policy that checks a profile
app/authorization_policies/members_only.liquid
---
name: members_only
redirect_to: /sign-in
---
{%- if context.current_user.id != blank -%}
true
{%- else -%}
false
{%- endif -%}This version checks only that someone is signed in. Add a check on the person's profile for a real members area.
Note
Profiles shipped by Insites modules are hidden from the list and cannot be edited. Facts from the Permissions module reference in the Insites Logic Engine.
Common mistakes
- Expecting a profile to restrict access on its own. Use a policy.
- Looking for roles or groups. The module has none in use; access is set by policies.
- Removing all contacts from a profile to test it. That removes their profile data too.