...
Tenant | A tenant represents a customer organization. A tenant will subscribe to the Yunibas application. The initial registration process will create a new tenant and the first user of that tenant. | |
User | A user is a tenant representative who, depending on their permissions, acts as an admin or power user for their tenant | |
Admin User | An Admin User is a User with exceptional permissions to see and manage all tenant data and settings
| A tenant admin is a user who can manage all aspects of their tenant, including managing users. |
| A persona admin user is granted permissions to manage assigned personas, including updating administrators and managers for the personas. | |
| A Persona Manager persona manager is a User user who has been assigned as a “Manager” in a Persona definition by an Admin Userto manage member personas assignments for the specified personas. | |
| A Standard User is a User user who is not an Admin User and does not currently have a Persona Manager assignmenta tenant admin and is not assigned a persona role. | |
Member | A member is a an exceptional person who needs access to tenant resources. A member can then be assigned to one or more personas. |
🥸 Other Terminology
Persona | A persona is a categorical representation of member access. This is synomous with the term “Business Role”. Personas are managed by Users and assigned to Members. Admin Users have access to manage Personas. Admin Users can assign a Persona Manager role to other Users. A Persona Manager has access to assign and expire Member associations. |
Permissions | Permission define granular authorization for Users. Admin Users can modify the default Permissions for their Tenant as needed. |
API | In this context, API refers to the settings that enable external systems to consume and publish data to a tenant. |
Webhooks | Webhooks allow Yunibas to contact external REST API’s as events occur so that updates can be sent in real-time. |