| Role | Description | Resource Resolver |
|---|---|---|
| supplier | The supplier role is endorsed by people providing deliverables for your software. This role is usually assigned to a development team member responsible for components releasing actions such as tagging in versioning / configuration management tool and making new component version available. In Join, this role has to be bound to a specific type of deliverables. Thus, it uses a specific implementation of PermissionResourceResolver. | org.figure8.join.services.security.DeliverableTypeResolver |
| manager | In Join system, a manager is a person responsible for creating new assemblies and deciding of staging environment upgrades using these assemblies. Such a role is usually assigned to project managers for the first steps of staging process and to quality officers for later steps. For better control, this role has to be bound to a specific environment. Because environments in Join are associated to a staging process step and a software release, this allows - for example - to declare a person being manager only for the "Non regression validation of release 2.0" and not for the "End users validation of release 2.0". | org.figure8.join.services.security.EnvironmentResolver |
| joiner | The joiner role describes a person that is one of the main users of Join : the staging or integration team member. As a member of this team, a joiner will use the Join frontend for most of its tasks : monitoring / managing artifact constructions and environment upgrades, checking environment configurations, scheduling and automating new tasks or new treatments... This role is not bound to a specific resource : it ia a global scoped security role. | None |
| admin | None |