UI integration is handled via the insights.chrome object that all front-end repositories have access to, a simple implementation of this can be seen here.

But the coles notes are below:

    const [ rbac, setRbac ] = useState<Rbac | undefined>(undefined);
    
    useEffect(() => {
        waitForInsights().then(insights => {
            insights.chrome.auth.getUser().then(() => {
                fetchRBAC(Config.appId).then(setRbac);
            });
        });
    }, []);

There will be additional work needed to create the context hook to parse/store the above, and to implement the boolean based permissions on editable actions (i.e.  create/edit/delete).

Permissions are as follow: 

Un-entitled: means you have no access to generic console dot apps, if you don’t have at least entitlement, you get redirected to the home screen without  a message as to why when you try to navigate where you shouldn’t.

Entitled: No read/write access > you get a screen when you arrive on an app without permissions, telling you don’t have access, speak to an admin.

Read permissions: C(r)UD actions are Disabled, offering tooltips that one doesn’t have permissions to perform said action.

Write: Complete access.