Chrome tab availability for specific role user in service operations workspace

[axtsxna]

Hi, I am working on Service Operations Workspace and want this chrome tab ("New Change Request") to be available for just a specific role user and not itil. How can I achieve this with ACL's ?

[Tai Vu · Accepted solution]

Hi @axtsxna 

That tab is managed through UX Page Property named chrome_tab.

At the condition > tableDescription > canCreate, this is only visible if the user can create a record on that table.

So you can change the ACL Create in the table to control the visibility of the item accordingly.

{
    "label": {
        "translatable": true,
        "message": "New Change Request"
    },
    "routeInfo": {
        "route": "create-change-request-page",
        "fields": {},
        "multiInstField": ""
    },
    "condition": {
        "tableDescription": {
            "table": "change_request",
            "canCreate": true
        }
    }
}

In the other hand, if you wouldn't like to change the ACL, you can modify the property by adding new attribute roles into the condition to apply specific for workspace.

Sample

{
    "label": {
        "translatable": true,
        "message": "New Change Request"
    },
    "routeInfo": {
        "route": "create-change-request-page",
        "fields": {},
        "multiInstField": ""
    },
    "condition": {
        "tableDescription": {
            "table": "change_request",
            "canCreate": true
        },
        "roles": ["admin"]
    }
}

Cheers,

Tai Vu

[Tai Vu]

Hi @sayali97

Yes, the user must pass the ACL check first, meaning they need the proper access rights to interact with the sc_cat_item table.

The Roles attribute in the tab configuration is used only to control who can create new records by using the "+" icon on the Chrome tab in SOW. It doesn’t override ACLs.
Think of it like trying to open a locked door with a badge. The tab might say "you’re allowed," but if ACLs say no, the system won’t let you in.

In that case what needs to be done?
We’ll need to review the ACLs for the sc_cat_item table and confirm whether the assigned role actually grants Create access. Adjust them according to your business requirements.

Cheers,

Tai Vu

[sayali97]

Hi @Tai Vu 

Thank you for your update. I found it why this happened it's not the ACL it's the condition written in the JSON if we remove that condition its accessible to the ITIL user as well and now it's working fine for me. The code is:

{
"label": {
"translatable": true,
"message": "New Request"
},
"routeInfo": {
"route": "record",
"fields": {
"table": "sc_cat_item",
"sysId": "-1"
},
"multiInstField": "sysId"
}
},