User Guide: Access and Use Apps
Preview Feature
This Preview feature is still being developed. We do not recommend using it in a production environment, because the feature might not be fully tested or optimized for performance, and related documentation could be incomplete.
Please continue to submit feedback through normal Cribl support channels, but assistance might be limited while the feature remains in Preview.
Use this guide to find, launch, and use Apps installed in your Organization.
In Apps (Preview), if you can see an App on the Apps page, you can open and use it. You only see installed Apps your administrator (or delegate) has granted you App user access to. You must still be an Organization member with access to at least one Cribl product (Stream, Edge, Search, or Lake). For who can create, install, share, and run Apps, see Roles, Permissions, and Governance in the Admin Guide.
Find and Open Apps
You run Apps that an administrator installed and shared with you. Installation and sharing are administrator tasks. See Install an App in the Admin Guide when you need that background.
Which Apps Appear in Your List
Apps lists only installed Apps for which you have App user access. If the list is empty, your Organization might not have installed Apps yet, or you might have No access to Apps that other Members use. Ask an administrator to install the App and assign App user when you need access.
Cribl Marketplace shows Apps that Cribl publishes. You can browse there to learn what is available or to read an overview before you ask an administrator to install an App. Browsing does not install anything.
Run an Installed App
From Stream, Edge, Search, or Lake, select Apps in the top bar to open a popover with up to six installed Apps you can launch directly. Select View All to open the full Apps inventory.
When an App opens, it fills the main content area and hides the product sidebar until you return to the product through the top bar.
Display name, ID, version, and author help you confirm that you opened the intended App or explain issues to your administrator.
Configure App Settings
App Settings is available only to Organization administrators. Members who run an App do not see App Settings in the Apps inventory or inside the App. If an App needs hosted keys, secrets, or outbound API review, ask an administrator.
To see how an App was installed, open App Settings > General and review Source.
Administrators open App Settings in either of these ways:
- In the Apps inventory, select Settings on the App’s row.
- Or open the App, then select the Settings (gear) icon in the App toolbar.
The App Settings screen has three tabs. General opens by default.
- General: Read-only App ID, Display Name, Description, Author, Version, and install Source. See General Tab in the Admin Guide.
- Key-Value Stores: List, add, edit, or delete KV keys and values for this App. Changes apply Organization-wide for this App’s KV namespace. Add API keys and tokens only as encrypted entries.
- External API Access: Review how outbound calls to external APIs are governed for this App and your Organization. Outbound access is on by default. The App must still declare external hosts in
proxies.yml.
For quotas, seeding, and related procedures, see Manage App Settings and External API Access in the Admin Guide.
Bookmark and Share App Links
Apps support deep linking when the builder uses a router that syncs in-App routes to the browser URL. As you move through an App’s tabs or multi-step workflows, the address bar usually updates to reflect your location.
In Safari, in-memory routing keeps the browser URL stable while you move inside the App. Shared links and bookmarks open the App entry screen. See Browser Support.
A typical App URL looks like this:
/apps/a/my-app/settings/general?tab=advanced
You can bookmark these URLs to return to the same view later, or copy and share them with teammates. When a teammate opens the link, Cribl restores the App state only if they are allowed to open that App (for example they have been granted App user for that App).
Understand Permissions and Errors
Apps run API calls with your existing product permissions (Stream, Edge, and Search). They do not grant extra access to those APIs. If you cannot perform an action in the Cribl UI, the App cannot perform it for you.
Your administrator assigns App user or No access per installed App. App user lets you open that App and use its App-scoped KV and proxy paths. It does not widen your underlying product roles.
For the full access model, see Roles, Permissions, and Governance in the Admin Guide.
Common Permission Scenarios
| What You See | What It Means | Next Steps |
|---|---|---|
| Installed list is empty but colleagues see Apps | You may have No access for those Apps, or you lack product membership. | Ask your administrator to assign App user for the Apps you need, and confirm you have access to at least one Cribl product. |
| “You don’t have permission” or a 403 error | Your product role cannot access the resource the App is calling. | Ask your administrator for the required Stream, Edge, Search, or Lake roles. |
| Disabled buttons or grayed-out actions | The App detected that you lack write access and disabled the action. | You can still view data, but you cannot make changes. |
| Partial data (for example, only some Worker Groups are visible) | You can access only a subset of resources. | This is expected. The App shows only what you are allowed to see. |
| Empty state with no data | Either no data exists yet, or you cannot view it with your current permissions. | Ask your administrator if you expected to see data here. |
If you are unsure which permissions an App needs, check the App’s first-run screen or contact the App builder.
Troubleshooting Quick Reference
| Problem | Resolution |
|---|---|
| You see the Apps page, but not the App you need | The App is not installed, you have No access, or your product role cannot view it. Contact your administrator. |
| The App opens but shows an empty screen | Try a full page reload. If it still happens, the App might have a defect. Report it to your administrator or the App builder. |
| A shared deep link does not load correctly | The link might point to a state you cannot access, or the App version changed after the link was created. Open the App from the Apps table instead. |