> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/standard-registry/policies/roles-and-groups.md). # Roles and Groups In Guardian, the concept of "Roles and Groups" plays a pivotal role in managing user access and permissions across different operations within the platform. This segmentation is designed to ensure that users have access only to the functionalities necessary for their role, enhancing both security and operational efficiency. ### Roles and User Activities Roles within Guardian are predefined sets of permissions that determine what actions a user can perform and what parts of the system they can access. These roles are crucial for partitioning user activities and tailoring the user experience to meet the needs of specific operational functions within an organization's sustainability initiatives. For instance, roles are utilized in the creation and management of policies, where different user groups are given specific responsibilities. An example of this is the differentiation between users who can submit documents for approval and those who have the authority to approve or reject these documents. This distinction ensures that the process of document verification and validation is streamlined and secure. Another critical use of roles is in the context of token operations, where users are assigned specific roles related to the creation, management, and distribution of digital tokens. These tokens often represent environmental credits or assets, and their management is subject to strict regulatory and organizational guidelines. ### User Groups User groups within Guardian are collections of users who share a common role or set of permissions. This grouping mechanism allows for easier management of access rights and simplifies the process of assigning and revoking permissions. By categorizing users into groups, administrators can efficiently implement changes across a broad set of users, ensuring that everyone within a group has the appropriate level of access to the system's functionalities. The segregation of users into distinct roles and groups is a testament to Guardian's commitment to providing a secure, customizable, and efficient environment for managing digital environmental assets. By carefully defining and managing roles and groups, Guardian enables organizations to optimize their sustainability efforts, ensuring that each user has the tools and permissions necessary to contribute effectively to their environmental goals. In conclusion, the "Roles and Groups" framework within Guardian is a foundational element that supports the platform's ability to offer tailored access and permissions. This ensures that users can efficiently and securely participate in the creation, management, and verification of digital environmental assets, all while adhering to the organization's specific operational requirements and sustainability objectives. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guardian.hedera.com/docs/develop/guardian/standard-registry/policies/roles-and-groups.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.