Organizations Overview

  • Updated

Overview

Organizations in Osano are a powerful, optional feature that allows you to group users based on common attributes, such as location, department, or teams. This grouping provides an additional layer of control over what users can access within the Osano platform when used in conjunction with user roles.

 

Key Features of Organizations

  • Grouping Users: Organizations allow you to categorize users into groups based on shared characteristics (e.g., Location, Department, Teams). This categorization can then be used to manage access to specific Osano features and configurations.
  • Access Control: By assigning users to specific Organizations, you can restrict their access to particular configurations and data relevant to those Organizations. This ensures that users only see and interact with the data they need.

Organizations are entirely optional in Osano. Not all customers may need or want to use this feature, but it can be particularly useful in scenarios like:

  • Multiple Businesses: If you manage multiple distinct businesses, you can restrict a web developer’s access to only the consent configurations relevant to their assigned business.
  • Parent Companies with Sub-companies: If your company has several sub-companies, each with its own DSAR form, you can limit access to these forms and associated requests to specific teams.

Where Organizations Can Be Used

Organizations can be assigned to the following:

  1. Users
  2. Consent Manager Configurations
  3. DSAR Forms and Data Stores

Only ADMIN users have the authority to assign Organizations to other users.

 

Users

  • Role-Based Access: Users assigned to Organizations will have access to CMP configurations and DSAR forms linked to those Organizations, as long as their roles permit such access. They can also access CMP configurations and DSAR forms not associated with any Organization.
  • Administrator Access: Administrators are automatically assigned to all Organizations, and this cannot be changed. If the administrator role is later removed, the Organization assignments will persist, but they can be modified or removed from non-administrator roles.

Note: If a user is not assigned to any Organization, they will have access to all data related to their user role across all Organizations.

 

Consent Manager Configurations

  • Organization-Specific Access: Administrators and Consent Managers can assign specific Consent Manager Configurations to one or more Organizations. This setup ensures that only users who belong to those Organizations and have the necessary roles can access these configurations.

    Exception for Unassigned Users: Users who have the correct roles but are not assigned to any Organization will still be able to access all Consent Manager Configurations across the platform.

 

DSAR Forms and Data Stores

  • Targeted Access Control: Administrators and Data Subject Owners can link DSAR Forms and Data Stores to specific Organizations. This limits access to those forms and their submissions to users who belong to the assigned Organizations.

    Exception for Unassigned Users: Users with the appropriate roles but not assigned to any Organization will still have access to all DSAR Forms and their submissions across the platform.

 

Important Notes

After adding or modifying Organizations for a user, you may need to refresh the page for changes to take effect.

The interplay between user roles and Organizations provides granular control over what users can see and do in Osano. Understanding this interaction is crucial for effective access management.

By strategically using Organizations, you can ensure that users within your Osano environment only access the data and configurations necessary for their specific role and responsibilities. This not only enhances security but also simplifies the user experience by reducing clutter and focusing on relevant content. Check out the Using Organizations documentation for details on setting up Orgs.