User with Contributor Role Unable to Checkout Branches or Create New Workspaces

Hi nilendraFabric ,

Thank you for your response. I understand that Contributors have limited permissions compared to Members and Admins. However, the Microsoft Fabric Git integration documentation suggests Contributors should be able to checkout branches and create workspaces as part of the Git workflow.

Could there be additional settings or restrictions causing this, or is the documentation outdated? I’d appreciate further clarification.

Thanks again!

Thank you for sharing the link to the Microsoft documentation. I have reviewed the resource, and it confirms that workspace roles such as Admin, Member, and Contributor should have the ability to "Branch out to new workspace."

Current Setup:

• As the Fabric Admin, I have enabled the organization-wide setting to allow workspace creation for all users.

Issue Observed:

1. Users with the Contributor role do not have access to the "Branch out to new workspace" option (it remains disabled).

2. When I upgrade the user’s role to Member, the option becomes enabled, but attempting to use it results in an error.

3. The feature functions only when the user is assigned the Admin role, which is not ideal from a security and governance perspective.

Request for Further Assistance:

• Are there additional prerequisites or configurations required beyond the documented settings?

• Could this be a potential issue with role-based permissions or a system limitation?

I would appreciate any further insights or troubleshooting steps to resolve this discrepancy. Thank you in advance for your support!

You're absolutely right—this limitation can be quite frustrating, especially when trying to maintain a least-privilege access model. It's not as straightforward as it is in Synapse or Data Factory.

To work around this, we’ve adopted a mitigation strategy by introducing an intermediary collaboration workspace. Here's how we approach it:

We start with a primary workspace, for example, contoso_wsp[Dev]. As an admin, I create a secondary workspace named contoso_collaboration_wsp. I then assign contributor users as admins to this collaboration workspace—not to the original one. This setup gives them the permissions needed to create their own development branches or workspaces (e.g., contoso_collaboration_wsp_contributor1, contoso_collaboration_wsp_contributor2, etc.).

Once their work is complete, I review and merge changes from these contributor workspaces back into the main contoso_wsp [Dev].

While it’s a bit of an overhead and certainly not ideal, this structure helps us maintain control over the dev environment while enabling contributor-level users to work independently.

That said, I’d be keen to hear how others are overcoming this challenge and whether there are any updates on how Microsoft Fabric plans to mature its support for DevOps/DataOps and CI/CD workflows.