Delegated Developer cannot see "create new spoke" in Workflow Studio

brianthomas24
Tera Contributor

Hi,

I have a group that is for developers who would be able to create a spoke. This is to use a DemoHub Narrative for Spoke Generation. This group is designed to be non-admin but they are power users and have many of the power roles, sub-admins etc. Whatever I do, I cannot seem to get members of this group to be able to see create new Spoke under Workflow Studio. Any advice?
The users have a lot of roles including delegated_developer, connection admin, all the roles for Flow Designing that I am aware of but this one part still shows as missing from the menu. See picture.
Thank you!

1 ACCEPTED SOLUTION

Ravi Gaurav
Giga Sage
Giga Sage

Hi @brianthomas24 


The below Details is from Community and product documentations:

Key Facts about Spoke Creation

  1. Only system administrators (admin) can create spokes by default.

    • This is intentional — a spoke is a global app extension and can impact the platform.

  2. To delegate spoke creation, you need App Engine Studio / Flow Designer App Creator entitlements.

    • Specifically, roles like:

      • spoke_creator (added in recent releases)

      • sn_fd_spoke_write (older releases)

    • Without these, the “Create Spoke” option is hidden in Workflow Studio.

  3. Delegated Developers can:

    • Create/update Flows, Actions, Subflows.

    • Work on existing spokes if they have access.

    •  But they cannot generate a new spoke unless given the spoke-creator entitlement.

  4. DemoHub Narrative / spoke generation features are still gated behind the same permission check.

What to Do

  • Check roles on the group:

    • Add spoke_creator (if you’re on San Diego+ release)

    • Or add sn_fd_spoke_write (for older releases).

  • Confirm the Studio app scope:

    • Users must have access to the application scope where they’re creating the spoke.

    • Add them as developers to that scope via Studio > Manage Developers.

  • If still hidden → check system property:

    • com.glideapp.app_creator.spoke_creation.enabled must be true.

    • Sometimes in non-admin environments, this is off.

Summary

Even with delegated_developer + Flow Designer roles, Create Spoke won’t show unless you explicitly grant spoke_creator (or sn_fd_spoke_write) + app developer access.

--------------------------------------------------------------------------------------------------------------------------


If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!

Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI

 YouTube: https://www.youtube.com/@learnservicenowwithravi
 LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/

View solution in original post

2 REPLIES 2

Ravi Gaurav
Giga Sage
Giga Sage

Hi @brianthomas24 


The below Details is from Community and product documentations:

Key Facts about Spoke Creation

  1. Only system administrators (admin) can create spokes by default.

    • This is intentional — a spoke is a global app extension and can impact the platform.

  2. To delegate spoke creation, you need App Engine Studio / Flow Designer App Creator entitlements.

    • Specifically, roles like:

      • spoke_creator (added in recent releases)

      • sn_fd_spoke_write (older releases)

    • Without these, the “Create Spoke” option is hidden in Workflow Studio.

  3. Delegated Developers can:

    • Create/update Flows, Actions, Subflows.

    • Work on existing spokes if they have access.

    •  But they cannot generate a new spoke unless given the spoke-creator entitlement.

  4. DemoHub Narrative / spoke generation features are still gated behind the same permission check.

What to Do

  • Check roles on the group:

    • Add spoke_creator (if you’re on San Diego+ release)

    • Or add sn_fd_spoke_write (for older releases).

  • Confirm the Studio app scope:

    • Users must have access to the application scope where they’re creating the spoke.

    • Add them as developers to that scope via Studio > Manage Developers.

  • If still hidden → check system property:

    • com.glideapp.app_creator.spoke_creation.enabled must be true.

    • Sometimes in non-admin environments, this is off.

Summary

Even with delegated_developer + Flow Designer roles, Create Spoke won’t show unless you explicitly grant spoke_creator (or sn_fd_spoke_write) + app developer access.

--------------------------------------------------------------------------------------------------------------------------


If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!

Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI

 YouTube: https://www.youtube.com/@learnservicenowwithravi
 LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/

I found your explanation to be excellent. If I have any follow up questions I will come back.