Not every app needs to be visible to everyone in your organization. Vybe gives you three levels of app access so you can control exactly who sees what — from shared team tools to personal works in progress.
Access levels
| Level | Who Can Access | Use Case |
|---|
| Organization (default) | All members of your organization | Shared team tools, company dashboards, org-wide utilities |
| Restricted | Only specific users you grant access to | Sensitive tools, department-specific apps, HR or finance apps |
| User | Only the app creator | Personal tools, prototypes, works in progress |
Setting the access level
Open app settings
Navigate to your app and open the Settings tab.
Find the Access section
Scroll to the Access section in the settings panel.
Choose the access level
Select Organization, Restricted, or User from the dropdown.
Organization access
This is the default. Every member of your organization can access the app. What they can do depends on their role:
- Owners, Admins, and Editors can view the deployed app and edit it via the AI chat.
- Members can view and use the deployed app but cannot edit it.
Use Organization access for shared tools that your entire team needs — dashboards, trackers, internal utilities.
Restricted access
Restricted access lets you share an app with specific people. Only users you explicitly grant access to can see or use the app.
Granting access to users
After setting the access level to Restricted:
- Open the Access section in app settings.
- Click Add User.
- Search for the team member by name or email.
- Select their access role:
| Access Role | What they can do |
|---|
| Viewer | Can access and use the deployed app |
| Editor | Can access the deployed app and edit it via the AI chat |
- Click Add to grant access.
You can add as many users as you need. Each user’s access role is independent — you can have some users as Viewers and others as Editors on the same app.
Use Restricted access for sensitive apps like HR tools, finance dashboards, or admin panels that only specific team members should see.
User access
User access makes the app visible only to you — the person who created it. No other member of your organization can see or access it.
This is ideal for:
- Personal tools you are building for your own use
- Works in progress that are not ready to share
- Prototypes you want to test before opening up to the team
When you are ready to share, change the access level to Organization or Restricted.
Path-level access
Beyond controlling who can access an entire app, you can restrict specific pages or routes within an app to specific users. This lets you build a single app with different sections for different audiences.
How it works
- Open your app’s Settings tab.
- Navigate to the Path Access section.
- Click Add Path Rule.
- Enter the path you want to restrict (for example,
/admin).
- Select which users can access that path.
Example
Suppose you have a team management app where most pages are accessible to everyone, but the /admin page should only be available to team leads:
| Path | Accessible to |
|---|
/ | All app users |
/dashboard | All app users |
/admin | Team leads only |
Path-level access works on top of the app’s access level. A user must first have access to the app itself (via Organization, Restricted, or User access) before path-level rules apply.
Creator access
The app creator always has full access to their app, regardless of the access level setting. Even if you set an app to Restricted and do not add yourself to the access list, you can still view and edit the app.
What is next
