In NWC , it appears that all users with Designer rights have access to edit all workflows in the tenant and use all connections created by other users as well. What are the plans to allow more granular permissions?
In the future, will the following be possible:
Solved! Go to Solution.
It would be useful if this works with NWC Groups and not individual users. Example:
User A is member of the group HR and could therefor edit all workflows/use all connections related to that group. A user could be member of multiple groups. An admin is member of all groups. Having admins per group seems useful for big companies.
Thanks for the feedback/suggestions. We absolutely intend to add permissions to connections and workflows, and we realize we'll need more granularity in permissions. A few things we are considering:
1.) Role/group based permissions. IE, someone in HR by default gets access to only HR workflows and specific connections such as perhaps ADP or Workday.
2.) Specific permissions - when creating a connection or workflow, allowing the designer to designate who has access. This can get tricky, as we'd need an additional page to manage this since users will be added and removed quite often.
If you have any other specific requests/requirements about how you'd like these permissions to behave, please feel free to add those!
The Xtensions framework (soon to be available in advance preview later this month) will support multiple authentication mechanisms including generic OAuth. The framework works with any API as long as the API on the back-end is:
I need to inquire about the timeline for OAuth on External Start. I will get back to you and this thread early next week on that feature specifically.
I wanted to get back on the OAuth question specific to External Start. As we mature our API interface with more functionality, we plan to use OAuth as the authentication mechanism. It’s too early to say for sure if we will tie in External Start. However it is something we would look at closer to the time. No set timeline yet.