[Due for payment 2025-11-07] [CMB] [$250] Don't show `New workspace` button when the restrict policy creation security group is enabled

[trjExpensify]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.2.22-6
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: None
Issue reported by: @JmillsExpensify

Action Performed:

1. Be a member on a private domain with the enableRestrictedPolicyCreation securityGroup setting enabled (Ref)
2. Go to Workspaces tab
3. Observe the New workspace button
4. Click the New workspace button
5. Observe it error out.

Expected Result:

This domain securityGroup setting prevents users from creating workspace, so let's hide the button like we do on Classic.

Note: Please make sure to also hide the "New workspace" button in the global create FAB as well.

Actual Result:

The button shows and creating a workspace errors out

Workaround:

Yes, disable the domain security group setting.

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021976385824389659939
• Upwork Job ID: 1976385824389659939
• Last Price Increase: 2025-10-09

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021976385824389659939

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

[melvin-bot]

Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

[paulnjs]

🚨 Edited by proposal-police: This proposal was edited at 2025-10-09 20:41:48 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

The button shows and creating a workspace errors out

What is the root cause of that problem?

We're always showing the new workspace button

App/src/pages/workspace/WorkspacesListPage.tsx

Line 472 in 1d055c2

const getHeaderButton = () => (

App/src/pages/home/sidebar/FloatingActionButtonAndPopover.tsx

Line 181 in 1d055c2

const shouldShowNewWorkspaceButton = Object.values(allPolicies ?? {}).every((policy) => !shouldShowPolicy(policy as OnyxEntry<OnyxTypes.Policy>, !!isOffline, session?.email));

What changes do you think we should make in order to solve the problem?

We should hide the new workspace button here if the restrict policy creation is enabled. To check this we can use the isRestrictedToPreferredPolicy data from usePreferredPolicy

const getHeaderButton = () => {
    if (isRestrictedToPreferredPolicy) {
        return null;
    }
    return (
        <Button
            accessibilityLabel={translate('workspace.new.newWorkspace')}
            text={translate('workspace.new.newWorkspace')}
            onPress={() => interceptAnonymousUser(() => Navigation.navigate(ROUTES.WORKSPACE_CONFIRMATION.getRoute(ROUTES.WORKSPACES_LIST.route)))}
            icon={Expensicons.Plus}
            style={[shouldUseNarrowLayout && [styles.flexGrow1, styles.mb3]]}
        />
    )
};

App/src/pages/workspace/WorkspacesListPage.tsx

Line 472 in 1d055c2

const getHeaderButton = () => (

Do the same here

const shouldShowNewWorkspaceButton = Object.values(allPolicies ?? {}).every((policy) => !shouldShowPolicy(policy as OnyxEntry<OnyxTypes.Policy>, !!isOffline, session?.email)) && !isRestrictedToPreferredPolicy;

App/src/pages/home/sidebar/FloatingActionButtonAndPopover.tsx

Line 181 in 1d055c2

const shouldShowNewWorkspaceButton = Object.values(allPolicies ?? {}).every((policy) => !shouldShowPolicy(policy as OnyxEntry<OnyxTypes.Policy>, !!isOffline, session?.email));

Other places we can discuss in the PR phrase

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

undefined

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[samranahm]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.