Access

Under the Access configuration pages, organizations setup

• Users,
• Roles, and
• API Tokens.

The navigation path is Configuration | Access.

Why Configure Access

Proper access configuration is fundamental to maintaining a secure and well-governed Hydden implementation. By strategically managing user accounts, assigning role-based permissions, and provisioning API tokens, organizations can:

• Enforce the Principle of Least Privilege: Ensure users and applications only have access to the specific resources and data they need to perform their responsibilities, reducing the attack surface and limiting the impact of compromised credentials.
• Enable Audit and Compliance: Maintain detailed audit trails of who accessed what data and when, supporting regulatory compliance requirements and security investigations.
• Support Organizational Governance: Align system access with organizational structure and job functions, enabling segregation of duties and preventing unauthorized actions.
• Facilitate Secure Automation: Issue and manage API tokens for programmatic integrations and automated workflows, enabling secure system-to-system communication without sharing user credentials.
• Streamline Offboarding: Quickly revoke access when users leave the organization or change roles, preventing unauthorized access by former employees or those outside their new responsibilities.