How Restricted Fields Work in Camphouse
⚠️ Note that you need Admin access to restrict fields.
Restricted Fields allow administrators to hide specific data fields from selected users or teams, ensuring that sensitive information stays protected across the platform. When a field is restricted, it becomes invisible for those users everywhere in Camphouse (sheet views, calendars, charts, and other areas where the field would normally appear).
This feature helps organisations collaborate securely. You can share access with external partners without exposing pricing, budgets, financial details, or internal data that shouldn’t be visible outside your team.
Using Restricted Fields provides clear benefits: it protects sensitive information, ensures that users only see what is relevant to their role, supports secure collaboration across different organisational structures, and reduces the risk of revealing confidential data by accident.
Fields That Can Be Restricted
The following field types support restriction rules:
• Number fields
• Calculation fields
• Text fields
• Template fields
• Generated fields
• Tag fields (limited release)
⚠️ Protected tag categories cannot be restricted.
Because Camphouse supports multi-level organisations (Global parent plus subsidiaries), it is important to understand how these restrictions behave across different levels.
How Team-Based Restrictions Work
Restrictions Applied at the Global Level Cascade Down
If a Team is created at the Global (parent) level and a restricted field is assigned to that team, this restriction automatically cascades to all subsidiaries. All users in that Global team inherit the same restrictions everywhere they have access.
Example:
A Global-level team “Agency Planners” has the field “Agency Fee” restricted.
All subsidiaries inherit this restriction for every user in that team.
Note: Global teams are only visible in the Global organisation. To verify a user’s Global team membership, view the user from the Global level.
Users in Multiple Subsidiaries Need Restrictions Set Per Subsidiary
If a user has access to multiple subsidiaries and is not in a Global-level team, restrictions must be configured separately in each subsidiary. Restrictions only cascade when they originate from a Global team.
Team Membership at Different Levels Affects Inheritance
A common scenario:
A user belongs to a Global-level team and is also part of local teams in some subsidiaries.
In this case:
Global-level restricted fields always apply everywhere
Local subsidiary teams can add more restrictions
Local teams cannot remove or override restrictions coming from Global
This makes Global team configuration especially important because it defines restrictions organisation-wide.
When Restrictions Do Not Cascade
If a user is not in a Global-level team and restrictions are only set at the subsidiary level, then:
Restrictions apply only inside that subsidiary
They do not cascade to any other subsidiaries
This allows for flexible setups, for example:
Restricted in Subsidiary A
Full visibility in Subsidiary B
Different restrictions in Subsidiary C
Behaviour of Restricted Fields in Targets
Restricted fields behave slightly differently in Target hierarchies.
The names of restricted Tag fields remain visible
The values inside those fields remain hidden for restricted users
Example:
In a Target hierarchy, a restricted user may still see “Comments” displayed as a field name, but all Comments values will appear blank. This is expected behaviour.
When Media Type Ownership Affects Cascading
A special case affects how Global-level restrictions cascade into subsidiaries.
Cascading Only Works When the Global Parent Owns the Media Types
Global-level restricted fields will only cascade into subsidiaries if the Global parent is the Media Type owner.
If subsidiaries own their own Media Types:
The field IDs differ
Field names may differ
Therefore, Global-level restrictions cannot map automatically
In these cases, restrictions must be applied per subsidiary, even if the fields are similar.
Practical effect:
If Global owns the Media Types → cascading works consistently
If subsidiaries own them → configure restrictions separately in each subsidiary
Summary
Global-level Team restrictions apply everywhere across the organisation.
Subsidiary-level restrictions do not cascade and must be set individually.
Global restrictions always take precedence over subsidiary restrictions.
Targets display restricted Tag field names but hide their values.
Cascading only works when the Global parent owns the Media Types.
These rules help you maintain both consistency and flexibility when managing sensitive data in complex organisational setups.
Keep Growing with Camphouse
🎓 Camphouse Academy – tutorials & courses
💬 Support – send us a message, we’ll reply as soon as possible