Project space

A project is the business isolation boundary of the platform. APIs, data sources, environments, groups, governance rules, subscriptions and sessions all belong to a project; after switching projects, all lists and configurations switch accordingly.

Enter a project

After a successful login, a project selection panel appears with two types of operations:

• Enter an existing project: click a project card or switch projects in the dropdown panel.
• Create a new project: fill in the project name, API prefix and description, then create.

The project switcher at the top displays the current project (for example "Default"); click it to switch projects or manage projects.

Create a project

Field	Required	Rule
Project name	Yes	Used for display on the project card and in the switcher
API prefix	Yes	Unique across the platform; case and leading/trailing slashes are ignored when comparing
Project description	No	Description of the project purpose

After creation, the platform automatically:

1. Initializes the dev development environment and the production environment.
2. Binds the default execution service.
3. Initializes project membership, making the creator a project administrator.

API prefix

The API prefix participates in building open API addresses. Changing the project name does not change the paths of published APIs; the API prefix must be unique across the platform to avoid route conflicts between projects.

Members and collaboration

Project administrators can invite other users to join the project; at least two characters must be entered for a member search to be triggered.

Project role	Capabilities
Administrator	Invite/remove members, maintain project information, manage resources in the project
Member	Develop APIs and configure data sources and rules in the project; the data scope is still constrained by personal permissions

In the project dropdown panel you can:

• Switch the current project.
• View project members.
• As an administrator, remove members or delete the project.
• Open the project management panel to edit project information and add members.

Deleting a project

Deleting a project affects the APIs, configurations and memberships in the project and is irreversible. Before deleting, confirm that no other project is referencing this project's data sources or APIs.

Project isolation scope

Resource	Isolation
APIs and groups	Visible only in the current project; cross-project use requires group authorization or migration
Data sources	Visible within the project by default; can be authorized for use by other projects
Environments and releases	Maintained per project and initialized automatically when the project is created
Flow control, cache, IP and alert rules	Isolated by project + environment
Calling credentials	Owned by the current user, but the scope is based on API authorization
Subscriptions and approvals	Isolated by project and API
AI sessions and logs	Isolated by user + project

Cross-project data source authorization

Data sources can be authorized for access by other projects:

1. Click Authorize in the data source list.
2. Select the target project and confirm.
3. The authorized project can select the data source in APIs.
4. The authorized project cannot view or modify the data source connection information and account credentials.

When a data source is already referenced by APIs of another project, authorization cannot be revoked and the data source cannot be deleted.

Request context

The frontend automatically includes the following in all admin requests except login-related APIs:

X-Project-Id: 1

The backend ProjectContextInterceptor loads the project context accordingly. If the project context is missing or the project is not permitted, business APIs reject access.

Permissions and visibility

• Regular users can only see data they created, plus authorized groups and data sources.
• Project membership determines "whether you can enter a project"; menu permissions determine "which pages you can see after entering".
• The super administrator can perform management operations across projects, but the API list is still filtered by the current project by default.

Related reading: Permission model, Data source authorization.