Open tlawrie opened 2 years ago
Need to also update this to reflect whats available.
This is now implemented and the roles that are mapped to the User are dynamic in the database allowing for;
Current Team Roles are
The Permission is in the form of scope / principal / action
for example Workflow/64dc6d44129d2221bfc24f66/**
or **/64dc6d44129d2221bfc24f66/Write
Scopes can be a range of things such as Workflow, WorkflowRun, TaskTemplate, Action, etc.. essentially all the objects in the system. However for v4, we don't use Scope in any of the permissions, its always ** but the Scope is checked on all the endpoints.
Principal is the Team or Workflow ID
Action is Read, Write, Action, Delete.
The backend needs to have the role checks enabled. Right now the authorisation can fail and it doesn't cause an error. (Check logs for all calls and identify what roles need to be updated)
Is your request related to a problem? Please describe. A new set of roles for different features
Describe the solution you'd like
Describe the benefits or justification for this request Allows a more fine grained ability