Teams in Camphouse
⚠️ Only Admin-level users can create and manage teams.
With the Teams feature, you can efficiently manage your organization's members and quickly grant them different permissions based on their needs. This guide will help you manage teams and permissions within the application.
💡Before adding members to teams, ensure they are added to your account. Read this article to learn how to add users.
Accessing the Teams Feature
Navigate to Settings: Go to your organization's settings page.
Users and Roles: In the settings menu, select "Users and Roles".
Teams Tab: Click on the "Teams" tab.
Creating a Team
Click "Create a Team" button.
In the modal that appears, input a name and color for the team.
Click the "Create" button.
On the invite team members page, check the boxes next to the users you want to invite.
Click the "Invite" button.
The team's name and organization will appear at the top of the page under the topmost search bar. The selected users will be listed as members of the team.
Inviting Team Members
💡 One user can be part of multiple teams.
Click on the team you want to invite members to.
Click the "Invite" button above the team members list.
A list of users will be displayed. Check the boxes next to the users you want to invite.
Click the "Invite" button at the bottom-right.
Editing a Team
Click the team you wish to edit from the teams list.
Click the edit button (pen icon) beside the team's name.
In the modal that appears, edit the name and color of the team.
Click the "Save" button.
Removing Team Members
Click on the team from which you want to remove members.
Check the boxes next to the members you want to remove.
Click the "Remove" button located above the members list.
In the modal that appears, confirm by clicking the "Remove" button.
Deleting a Team
Click on the team you want to delete.
Click the delete button (trash can icon) beside the team's name.
In the modal that appears, click the "Delete" button.
Note: The team will be deleted but the users will remain in your account.
Restriction Options
User access can be restricted in two key ways: through the use of protected tags and by restricting fields.
ℹ️ User restrictions can also be applied individually without the need to create a team. For details on how to do this, please refer to this article.
Protected Tags
⚠️To restrict a whole tag category, please reach out to your Customer Success Manager.
Protecting a tag category means that users who do not have access will not see any entries in a plan that uses that tag. They will still see the tag category headers but only related values they have access to.
Steps to Protect a Tag Category and manage access:
1. Contact your Customer Success Manager to specify the tag categories you wish to restrict. They will update the settings for those categories on your behalf.
2. When the tag category settings have been changed by your CSM, go to the Teams section.
3. Click on the team you want to edit permissions for.
4. Go to Tag Permissions.
5. Choose the permission level for each protected tag category and tag (Admin, Editor and Viewer). You can also set permissions to "Full access". Any tags not selected will remain hidden from the user.
Example:
Protected Tag Category: Product
Granted Access: Product A
Restricted Access: Product B and Product C
A user with access to Product A will be able to view and create entries specifically for Product A, but will have no visibility or access to entries associated with Product B or Product C.
If a protected tag is used in plan setup, users without access to the tag will not see the plan anywhere.
How team and user tag permissions combine
Protected tag permissions can be set on a user, on a team, or both. They aggregate; they do not override. If a team gives a user access to additional tags in a protected tag category, those tags become visible to the user.
The role shown next to each tag (Admin, Editor, Contributor, Viewer) describes the user's level on that tag. Importantly, this role can only narrow what the user can do on entries with that tag below their Organisation Role; it can never raise them above it.
Example 1: visibility is widened by a team
A user has the Organisation Role of Viewer. They are added to a team that has Admin access to the tag "UK" in the protected Country tag category. The user can now see plans tagged with the UK, but they cannot edit, add, or delete those plans. They remain view-only on UK plans, because their Organisation Role is Viewer.
Example 2: actions are narrowed by a team on a specific tag
A user has the Organisation Role of Editor and full access to the Country tag category individually. They are added to a team that limits them to Viewer on the "Sweden" tag. On Sweden plans the user is view-only; on all other countries they remain Editor.
Example 3: full access aggregates
User level: Full access on the Country tag category. Team level: limited to a few countries. Result: the user keeps full access; restrictions aggregate and do not override.
💡 Tip: teams are often best used for grouping users with the same tag access pattern (e.g. by market, agency, or business unit). They are not a substitute for setting the correct Organisation Role on each user.
Viewing a user's effective tag permissions
When a user belongs to one or more teams, the Protected Resources tab on the user page shows two views: the tag permissions set directly on the user, and the permissions they inherit from team membership.
Note: both views appear only when the user is in at least one team. For users in no teams, the tab shows the user's own permissions matrix only.
To switch between views:
Go to Settings → Users and Roles.
Select the user.
Open the Protected Resources tab.
Above the matrix, switch between User role and Role in teams.
What each view shows
User role: the protected tag permissions set directly on this user.
Role in teams: the permissions inherited from team membership. Inherited entries appear with a dashed border and a small team icon — hover any entry to see which team it comes from.
When the user is in one or more teams, a blue info banner appears at the top of the tab, and an info (ⓘ) icon next to the view switcher explains the inheritance rule.
⚠️ Inherited tag permissions broaden the tags a user can see and the role label that applies to each tag. They do not change the user's Organisation Role. A Viewer at the Organisation level remains view-only on every plan, even if a team grants them Admin on a tag.
Restricted Fields
Restricting a field makes it invisible to users, hiding it in Sheet view and other views like Filter, Media Overview, Targets, Results, or Reports. This is useful for sensitive information like pricing.
⚠️ Start Date, End Date, and Media Vehicle and tags cannot be restricted.
Steps to Restrict Fields for Teams:
Go to the Teams section.
Choose the team for which you want to change settings.
Click on "Restricted Fields".
On the left, you will see a list of available fields to restrict. Click on the plus sign (+) for the fields you wish to restrict for this team.
Click save when done.
⚠️ To restrict fields for a specific subsidiary, navigate to that subsidiary and update the permissions accordingly.
Get Support
Have questions or need help? You can reach us directly via the messenger on camphouse.io or the contact support button located in the top right corner of the Camphouse App.
Learn More
Not a Camphouse user but interested in learning more? Book a demo with the Camphouse team today and start being more productive with your marketing.