Workspace and Folder Access

Use private folders to control which teams can see specific projects.

Workspace and folder access is your “scope control” layer. Use it to segment projects by team, function, or sensitivity.

Folder access works alongside:

• Role-Based Access Control (RBAC) (what users can do)

• Connection and Knowledge Base Permissions (who can view/use specific resources)

What folder access controls

Folders are public by default. When you make a folder private, only the allowed users and groups can see:

• the folder

• the projects inside that folder

This is the simplest way to ensure teams only see the projects meant for them.

Folder access controls visibility in the StackAI workspace. It does not replace interface security for published deployments (SSO, password, allowlists).

---

Make a folder private

Use private folders for projects that include sensitive data, regulated workflows, or restricted connections.

1

Open the folder settings

Go to the Projects dashboard. Find the folder you want to restrict. Open the folder’s settings menu.

2

Enable private access

Turn on Private Folder. Add the users and groups that should have access.

3

Confirm access

Verify that only the selected users and groups can see the folder and its projects.

Example: configuring a private folder and selecting who can access it.

Update folder access

You can update folder access at any time. Changes apply immediately.

To update access:

1. Open the folder’s settings.

2. Add or remove users and groups from the allowlist.

To make the folder public again, turn off Private Folder.

Best practices

• Prefer groups over individual users.

• Create dedicated folders for sensitive teams (Legal, Finance, HR).

• Keep production workflows in a restricted folder to reduce accidental edits.

How folder access interacts with permissions

Folder access is a visibility layer. It typically works like this:

• Folder access decides whether a user can see a project in the workspace.

• RBAC decides what that user can do after they can see it (build, edit, run).

• Connection and Knowledge Base permissions control who can view and manage those resources directly.

If a workflow uses sensitive connections or Knowledge Bases, do both:

1. Put the workflow in a private folder.

2. Restrict the connection / Knowledge Base to the same users or groups.

Settings visibility by role

The Settings menu depends on your role.

Admins

Admins can access all organization settings. This includes governance, security, and user management.

Settings menu for Admins.

Editors

Users & Viewers

Troubleshooting

I don’t see the “Private Folder” option

Your role may not include access to manage folders. Check your permissions in Role-Based Access Control (RBAC) or ask an admin to update your access.

A user can’t find a project

Confirm:

• The project is in the expected folder.

• The user (or one of their groups) is included in the folder allowlist.

• The user’s role allows the action they’re trying to take (view/run/edit).