Manage projects

A project belongs to a team and has its own schema, data, members, API configuration, and service settings. Most people create projects in Studio; the Dashboard’s project creation action creates an empty one.

Project ID

Open Settings → General → Project ID. Developers need it for the API endpoint, the CLI and a code-managed flexkit.config.ts; support may ask for it too. A display name is not a substitute for the ID.

Project name

Use General settings to give the project a recognizable name. The title Studio shows in its navbar is part of the schema and may remain different after a Dashboard rename; ask the agent to change it, or align both names deliberately.

Project avatar

The avatar helps distinguish projects in selectors. Changing appearance does not change the schema or the project ID. Use a non-sensitive image that remains recognizable at a small size.

Schema management

Open Settings → General → Schema Management to choose who may change the project’s schema. One channel owns it at a time:

• Managed in the app (default for new projects): the Flexkit Agent can propose schema changes from the chat. Each proposal shows the entities and attributes it adds, changes or removes, and nothing is deployed until an owner or developer approves it in Studio. flexkit deploy is refused while this mode is active.
• Managed from code: only flexkit deploy changes the schema. The agent can read the schema but refuses to change it. Projects that were deployed from the CLI before this setting existed start in this mode.

Switching is an owner-only action and is recorded in the project activity. Switching to the app does not change the deployed schema; your config file simply stops being the source of truth until you switch back.

Approval emails

When the Flexkit Agent or an automation proposes a change that needs a person’s approval, the request appears in Activity in Studio for the people who can decide it:

• Chat proposals go to the person who owns the chat.
• Automation proposals go to the person who created the automation, as long as they are still an owner or developer of the project.

Open Settings → General → Approval Emails to choose how long a request may stay unread before Flexkit also emails it: after 1, 2, 4, 8 or 24 hours (4 hours by default), or never. Opening Activity counts as reading the requests it shows. Each recipient gets at most one email per request, and requests that were already approved, rejected, cancelled or expired are not emailed.

Changing the delay is an owner-only action and is recorded in the project activity. The new delay applies to requests made after the change.

Connect people and applications

Invite people under Members. They work in the desktop or web app; the Open in Studio button in the project header opens the project there. Other systems connect through the API with API tokens, which belong in trusted server environments rather than public configuration files. Teams that self-host Studio share their own URL instead.

For pauses, read-only restrictions, and deletion, see project lifecycle. Review the selected project and team before making an administrative change.