--- title: How to Restrict What Team Members Can and Can't See description: You can have full control over which systems your team members can and can't view. --- [Skip to content](https://kb.systemology.com/help-center/how-to-restrict-what-team-members-can-and-cant-see#main-content) English Show submenu for translations ![1000X162.png\]](https://kb.systemology.com/hs-fs/hubfs/1000X162.png?width=250&height=43&name=1000X162.png) Open main navigation Close main navigation - English Show submenu for translations - [www.systemHUB.com](https://www.systemhub.com/) [www.systemHUB.com](https://www.systemhub.com/) How can we help? - There are no suggestions because the search field is empty. 1. [Help Center](https://kb.systemology.com/help-center?hsLang=en) 2. [Permissions & Roles](https://kb.systemology.com/help-center/permissions-roles?hsLang=en) # How to Restrict What Team Members Can and Can't See ## This article explains how to control what team members can and can't see in systemHUB using roles, assigned systems, and user permission levels. \[VIDEO COMING SOON\] --- ### **👤 Assigning Systems to Team Members** Each system or policy can have individual team members assigned to it. Depending on the user’s permission level, they may only be able to view systems that have been assigned to them directly. --- ### **🛠️ Steps to Assign Systems Directly** 1. Open the relevant system or policy. 2. Click **Edit**. 3. Locate the **Assigned Team Members** section. 4. Add the relevant users. --- ### **👥 Using Roles to Manage Access More Efficiently** Instead of assigning systems individually to each person, a more scalable approach is to assign systems to roles or departments. ### **🏢 Example Roles & Departments** - Accounting & Finance - Marketing - Operations - HR You can also create more specific roles, such as: - Google Ads Specialist - Sales Manager - Customer Support Lead --- ### **❓ Why Use Roles?** Using roles makes managing access much easier when team members join or leave the business. > **Example:** If a finance team member resigns, you won’t need to manually reassign every finance, related system. You simply assign the new team member to the **Accounting & Finance** role, and they’ll automatically gain access to all systems linked to that role. --- ### **🏗️ Creating and Assigning Roles** 1. Navigate to the **Roles** section. 2. Click **Create New Role**. 3. Name the role or department. 4. Assign relevant systems to that role. --- ### **📎 Assigning Roles to Team Members** 1. Go to **Team Members**. 2. Select the user. 3. Click **Edit**. 4. Add the appropriate role(s). 5. Click **Save changes**. Once assigned, the user will automatically gain access to all systems connected to that role. --- ### **📊 Understanding User Permission Levels** systemHUB includes four user permission types: - **Admin** - **Editor** - **Contributor** - **Reader** You can view the permissions for each level under the **Permissions** tab. > ⚠️ **Important Note:** Admins and Editors generally have access to all systems. Permissions based on assigned roles and systems mainly apply to Readers and Contributors. - **Example:** A Reader assigned to the **Accounting & Finance** role will only see systems linked to that role, though they may also see systems they’ve been individually assigned to. --- ### **🧪 Testing and Customising Permissions** ### **👁️ Viewing the Account as a Team Member** You can log in as a team member to verify: - What systems they can access - What actions they can perform - Whether permissions are working correctly This is a useful way to test and confirm access restrictions. ### **⚙️ Customising Permission Levels** The default permission settings can also be customised. You can enable or disable specific actions, restrict certain capabilities for each user level, and tailor permissions to suit your organisation’s needs. 1. Open the **Permissions** settings. 2. Review the available options. 3. Check or uncheck permissions as required. --- ### **🚀 Summary for Best Practice** Permissions in systemHUB are controlled through a combination of assigned systems, assigned roles, and user permission levels. For the most efficient setup, we recommend: - Assigning systems to roles or departments - Assigning team members to those roles - Using **Reader** or **Contributor** permissions where restricted access is required --- ### **🎉 You're All Set!** If you have any questions, feel free to reach out to the systemHUB support team. - [Getting Started](https://kb.systemology.com/help-center/getting-started?hsLang=en) - [Profile & Settings](https://kb.systemology.com/help-center/profile-settings?hsLang=en#main-content) - [Profile Setup & Onboarding](https://kb.systemology.com/help-center/profile-settings?hsLang=en#profile-setup-onboarding) - [Account Security & Access](https://kb.systemology.com/help-center/profile-settings?hsLang=en#account-security-access) - [Notifications & Preferences](https://kb.systemology.com/help-center/profile-settings?hsLang=en#notifications-preferences) - [Admin & Billing](https://kb.systemology.com/help-center/admin-billing?hsLang=en#main-content) - [Team & User Management](https://kb.systemology.com/help-center/admin-billing?hsLang=en#team-user-management) - [Subdomain & Organization Settings](https://kb.systemology.com/help-center/admin-billing?hsLang=en#subdomain-organization-settings) - [Billing & Subscriptions](https://kb.systemology.com/help-center/admin-billing?hsLang=en#billing-subscriptions) - [Permissions & Roles](https://kb.systemology.com/help-center/permissions-roles?hsLang=en) - [Building Content](https://kb.systemology.com/help-center/building-content?hsLang=en) - [Working With Content](https://kb.systemology.com/help-center/working-with-content?hsLang=en#main-content) - [Tagging & Organization](https://kb.systemology.com/help-center/working-with-content?hsLang=en#tagging-organization) - [Content & Collaboration Tools](https://kb.systemology.com/help-center/working-with-content?hsLang=en#content-collaboration-tools) - [Limits & Specifications](https://kb.systemology.com/help-center/working-with-content?hsLang=en#limits-specifications) - [Training](https://kb.systemology.com/help-center/training?hsLang=en) - [Reports & Compliance](https://kb.systemology.com/help-center/reports-compliance?hsLang=en) - [Integrations & API](https://kb.systemology.com/help-center/integrations-api?hsLang=en) - [Troubleshooting](https://kb.systemology.com/help-center/troubleshooting?hsLang=en#main-content) - [Technical Requirements & Compatibility](https://kb.systemology.com/help-center/troubleshooting?hsLang=en#technical-requirements-compatibility) - [Cache, Performance & Errors](https://kb.systemology.com/help-center/troubleshooting?hsLang=en#cache-performance-errors) - [Status, Requests & Affiliate Program](https://kb.systemology.com/help-center/status-requests-affiliate-program?hsLang=en#main-content) - [Affiliate Program](https://kb.systemology.com/help-center/status-requests-affiliate-program?hsLang=en#affiliate-program) - [Legal & Security](https://kb.systemology.com/help-center/legal-security?hsLang=en#main-content) - [Policies & Terms](https://kb.systemology.com/help-center/legal-security?hsLang=en#policies-terms) [![2026-02-02 - Logo - SYSTEMology - v11 - 2024](https://kb.systemology.com/hs-fs/hubfs/Logos/SYSTEMology/2026-02-02%20-%20Logo%20-%20SYSTEMology%20-%20v11%20-%202024.png?width=200&height=30&name=2026-02-02%20-%20Logo%20-%20SYSTEMology%20-%20v11%20-%202024.png "2026-02-02 - Logo - SYSTEMology - v11 - 2024")](https://www.SYSTEMology.com/) Copyright © 2026, SYSTEMology / systemHUB