Attribute permissions
Attribute permissions control access to an attribute's values on objects (e.g. salary, confidential notes) — not who can change the attribute's definition (name, type, configuration), which is managed separately. Use them to share most attributes broadly while restricting a few, or to apply different access per attribute.
Only space owners can configure attribute permissions — if you don't see the Permissions option, you're not a space owner.
Opening attribute permissions
Space configuration → Attributes tab → the attribute's ⋮ menu → Permissions.
Restriction types
- Open — everyone in the space can view and edit it; no per-user setup.
- Restricted — only explicitly added users can view or edit; everyone else in the space falls back to a configured default access level.
Access levels
| Level | Meaning |
|---|---|
| No access | Can't view or edit this attribute on objects. |
| Read | Can view its values. |
| Write | Can view and edit its values. |
For a Restricted attribute, set the default level for "everyone else," then add individual users with their own level (which overrides the default). Only space members can be added, you can't add yourself, and access can be changed or removed later from that user's row.
Rules to watch for
- If the attribute is the type's label or is required, restricting write access too far can leave people unable to create objects — Starhive warns you, but keep write access for at least some users or the default.
- Only space members can have attribute permissions — invite someone to the space first if they need access.
Click Apply to save, or close the modal to discard changes.