Settings overview
Settings in Flezise has two scopes. Platform settings apply organization-wide and become the inherited default for every project. Project settings inherit them and can override individual tabs for one project only.
Read this if you administer the platform or need to know what settings exist before configuring them.

Scope switcher
The Settings scope selector sits above the navigation list. Platform shows organization-wide configuration. Project: <name> switches to a single project; tabs that carry a project-level override show an override pill in the sidebar. Tabs not included in your plan stay in the navigation with a lock icon; hovering shows the reason.
Platform sections

Project sections
Project settings mirror most platform sections. The Project section adds tabs specific to a project: General ("Core project settings, repository connection, and service status."), Members, Groups, Approvals, Integrations, and Budget & Controls ("Set monthly spend and token budgets, alert thresholds, and automation cost caps."). The Workspace and AI Gateway tabs work as project-level overrides of the platform defaults.
Roles and groups
Platform access uses two roles: Member and Administrator. Either can carry the Can create projects checkbox; when enabled, new projects automatically add that person as Project Admin. Five groups are seeded automatically:
Project groups control only project-scoped permissions. Assigning a platform-wide bit (such as Manage Providers or SSO access) to a project group raises an error: "Platform-wide permissions cannot be granted to a group."
Permission categories
Permission bits are grouped into display categories in the UI: Artifacts (including Submit for Review and Approve / Reject), Members (Invite, Manage Roles), AI Gateway (Manage Providers), and further categories covering Projects, Knowledge, Pipeline, Repository, Integrations, and Settings.