Connected Apps
This guide explains everything you can do with the Connected Apps area in the BlueRange Portal. It is written for portal administrators. No technical background is required.
| Access is restricted. Connected Apps is available only to system-organization administrators. If you don’t see it in the menu, your account doesn’t have access. Depending on your assigned rights, some buttons or menu items described here may also be hidden. |
Introduction
Connected Apps lets you register the mobile apps that are allowed to access the platform, and control which organizations each app is allowed to see. You find it under:
Configuration → App Management → Connected Apps
Each connected app (also called an "app flavour") is identified by a unique App-ID. When the app shows its login screen, it uses this App-ID against the platform’s public login endpoint, and the platform returns only the organizations you have assigned to that app.
Each connected app has:
-
a Name – for you to recognize it;
-
a unique App-ID – the UUID the app was built with;
-
an Active / Inactive state
-
a list of assigned organizations.
| Access is tied to the App-ID and its assignment list. You can add a new app or grant an app access to more organizations at any time – without releasing a new version of the app. An app only ever receives the organizations on its own list, so it can never see another customer’s organizations. See more at Key concepts. |
The Connected Apps page
This is the page you land on when you click Connected Apps in the menu.
What you see
The page shows the total number of connected apps in a sidebar and a table listing all registered apps with a search box and adjustable columns. Use Create Connected App (top right) to register a new app. If no apps exist yet, a short message with a Create Connected App button helps you get started.
Creating or editing a Connected App
Choosing Create Connected App (or Edit) opens a dialog with these fields:
-
Name – required. A recognizable display name for the app. It must be unique and must not start or end with a space.
-
App-ID – required. The unique App ID (a UUID) that the app was built with; the public login endpoint uses it to identify the app. It must be a valid UUID and must be unique.
-
Active – switch the app on or off. New apps are active by default.
Click Save to apply, or Cancel to discard. Save stays disabled until all required fields are filled in correctly.
| Name and App-ID must each be unique across all connected apps. |
Assigning Organizations
From an app’s row menu, choose Assign Organizations to open the Assigned Organizations dialog. This controls which organizations the app is allowed to see through the login endpoint.
The dialog shows a searchable, multi-select list of organizations. Tick the organizations the app should have access to, untick any it should no longer see, then click Save to store the selection or Cancel to discard.
| Saving replaces the app’s entire assignment list with your current selection. An app with no organizations assigned will not return any organizations at login. |
Key concepts
App-ID. The App-ID is the unique identifier the app was built with. It is how the login endpoint recognizes the app and knows which organizations to return. Because access is tied to the App-ID and its assignment list, you can onboard new customers or grant more access purely from this page – no new app release is needed.
Enable / disable. Deactivating a connected app revokes its access immediately, without deleting it or losing its organization assignments. Reactivate it at any time to restore access. This is the recommended way to temporarily block an app.
Assigned organizations (the allowlist). Each app can be linked to many organizations, and an organization can be linked to many apps. An app only ever receives the organizations on its own list, which keeps every customer’s organizations separate from the others.