Introduction

Getting started

Walkthrough Guides

CafeX Apps

Workflows

Using CafeX Collaborate App

Reporting

Managing CafeX

Integrating CafeX

Security

App Studio

App Studio Components

CafeX Apps

Understanding App Permissions

Modified on Wed, 4 Dec at 1:15 PM

In most organizations, multiple team members need access to make changes and configure aspects of an App. Administrators and various teams often require permissions to manage and update the App.

 

Tenant Administrators have full administrative rights to configure all Apps across the organization. They can always see and manage any App in the system and grant App Builder permissions to other members of the tenant.

 

App Builders can create new Apps and access the App Studio. As an App Builder, you are responsible for managing the permissions for your Apps.

 

To configure permissions:

  1. From App Studio, click Configure > App permissions (). The Permissions page opens.

  2. Here’s what you can configure:

    Users allowed to configure this app
    : A list of App Builders who can edit the App. Only members of your tenant with the App Builder role can be added. If the list is empty, any App Builder can edit the App. If there is no option to add App Builders, it means that all available App Builders are already listed.

    Users allowed to create app workspaces: A list of users who can create new workspaces. If the list is empty, any member of your tenant can create workspaces for the App.

    Users allowed to view app analytics: A list of users who can access the App Analytics page.

    Access controls: A list of IP addresses or hostnames allowed to load the App. Typically, this is managed using a CIDR address range, so the app can only be accessed from a secure network, such as through a VPN with a predefined IP range.

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article