Project lifecycle and resource setup
A project is the main boundary for an Appwrite application. Its lifecycle creates a team-owned project record, connects the project to a data boundary and service settings, tracks early project use, and removes project-owned resources after deletion. See Project administration for the wider administration model, Platform configuration for server-wide settings, and Video processing API for media processing after project setup.
Project boundary
The project boundary gives each application its own identity and operating context. Platform data stores the project and its management state. Project data uses a project-specific tenant or namespace so application resources remain linked to their owner.
Project identity and ownership
A project has a unique ID, a name, a region, and an owning team. The team supplies the base access rules. Project-specific team roles can grant access to one project without granting access to every project in the team. src/…/Create.php and src/…/Permission.php.
The console project is a reserved system project for the Appwrite administration surface. It does not use the normal user-project creation path. app/…/console.php.
References: src/…/Create.php• L42-68 src/…/Permission.php• L18-35 app/…/console.php• L11-30
Project data boundary
Project data uses either shared tables with a project tenant or an isolated database namespace. Later requests use the same project identity to route data, which keeps resources associated with the project that owns them. src/…/Factory.php.
The platform database stores the project record and platform metadata. The project data store holds metadata for project resources. The collection configuration also defines the resource records used by project services. app/…/collections.php and app/…/projects.php.
References: src/…/Factory.php• L181-197 app/…/collections.php• L18-34 app/…/projects.php• L6-36
Creation flow
Project creation turns a valid request into a usable application boundary. The flow validates ownership and placement, writes the platform record, prepares the selected data layout, and returns an active project.
This diagram shows how a project request becomes a project with its data boundary and starting settings.
flowchart TD
A[Project request] --> B{Team exists?}
B -- No --> X[Reject request]
B -- Yes --> C[Validate ID and region]
C --> D{Project ID available?}
D -- No --> X
D -- Yes --> E[Create project record]
E --> F{Shared data layout?}
F -- Yes --> G[Use shared tables with project tenant]
F -- No --> H[Create isolated project namespace]
H --> I[Create project metadata and audit data]
G --> J[Run post-creation hook]
I --> J
J --> K[Return active project]
Request validation
The creation interface requires a project ID, a name, and a team. It can generate the ID when the caller does not provide a custom one. The system rejects the reserved console ID, duplicate IDs, missing teams, and regions that the deployment does not allow. src/…/Create.php.
The organization flow uses the organization’s current team as the owner. The general projects flow receives a team ID and checks it before creation. Both flows establish the same project boundary. src/…/Create.php.
References: src/…/Create.php• L42-74 src/…/Create.php• L40-83
Project defaults
Creation starts the project in an active state. It gives authentication and project operation a safe default policy. The project has no custom platforms, keys, or webhooks until an administrator adds them. Deployment authentication settings can add enabled methods to the default set. src/…/Create.php.
The project record also keeps the region, data-store route, team link, version, search values, and access permissions. These values let later requests locate the project and enforce its boundary. app/…/platform.php.
References: src/…/Create.php• L76-113 src/…/Create.php• L153-173 app/…/platform.php• L10-112
Resource setup
The data store is selected from pools that match the project region. A shared layout reuses prepared metadata tables and separates records by tenant. An isolated layout creates a project database and its metadata collections. The isolated layout also creates the audit store before creation completes. src/…/Create.php.
Server startup prepares the shared project database and its metadata collections. This setup is separate from project creation, so a shared layout does not need a new database for every project. app/http.php.
References: src/…/Create.php• L121-151 src/…/Create.php• L178-227 app/http.php• L401-467
Project management
Project management changes the project record or settings that control its services. Platform project operations read the project record. Resource operations use the resolved project context so requests from the console, an administrator, or a project key use the same project boundary.
Project metadata
Administrators can change the project name and descriptive or legal details without changing its data boundary. Project listing supports search, filters, cursor paging, and team-scoped results. A project read fails when the project context does not resolve to an existing project. src/…/Update.php, src/…/XList.php, and src/…/Get.php.
The project team can also change. A team transfer requires owner access on both the current and destination teams. It updates project access rules, refreshes permissions on linked installations, repositories, and version-control comments, and grants the new project owner access to the project database. This keeps ownership aligned across the project and its linked development resources. src/…/Update.php.
References: src/…/Update.php• L24-70 src/…/XList.php• L39-106 src/…/Update.php• L62-125 src/…/Get.php• L24-62
Service settings
Service settings control which optional Appwrite services a project can use. The project response exposes the configured service set and each service’s enabled state. A service without a stored override is enabled by default. The server configuration defines which service IDs are available. src/…/Project.php and src/…/ProjectService.php.
The same management area controls protocols and authentication methods. Each change updates the project settings, clears the cached project record, and publishes an event for other system parts. src/…/Update.php, src/…/Update.php, and src/…/Update.php.
Project management also covers settings that shape how project services operate. Custom SMTP can provide branded email delivery, project labels support organization-level filtering, and project variables provide values for builds and runtime use. These settings stay attached to the project and use project-scoped access rules. src/…/Update.php, src/…/Update.php, and src/…/Update.php.
References: src/…/Project.php• L163-188 src/…/Project.php• L273-319 src/…/ProjectService.php• L11-27 src/…/Update.php• L31-86 src/…/Update.php• L68-95
Video profiles
Video profiles are project-owned presets for media processing. A profile captures the target video and audio bitrates, dimensions, and codec so later video jobs can use a named processing choice. The create and list operations use the project data store, which keeps profiles inside the project boundary. src/…/Create.php and src/…/XList.php.
Profile creation accepts only codecs enabled by the deployment and rejects duplicate profiles. Profile listing filters by codec and supports query and cursor controls, while defaulting to a stable dimension order. The shared video rules supply the valid codec set and parameter limits. src/…/Base.php.
The profile endpoints are preview SDK operations until video support is generally available. They require project administration or a project key with the matching profile scope, and profile creation emits a project-scoped event for downstream handling. See Video processing API for the media flow that consumes these settings.
References: src/…/Create.php• L25-72 src/…/Create.php• L75-113 src/…/XList.php• L27-66 src/…/XList.php• L69-129 src/…/Base.php• L53-77 src/…/Base.php• L105-121 src/…/Base.php• L223-237
LDAP directory sign-in
LDAP directory sign-in lets a project use an external directory for user authentication. Project settings hold the directory connection and user mapping rules. The project must have directory hosts and a search base before LDAP can be enabled. src/…/Update.php and src/…/Update.php.
An LDAP configuration change can validate the directory before the project remains enabled. A separate test checks the stored connection and service account. It can also look up a user and verify that user’s password and required group without signing the user in. src/…/Create.php.
This diagram shows how LDAP settings move from project management into a usable sign-in path.
flowchart LR
A[LDAP settings] --> B[Validate connection settings]
B --> C{LDAP enabled?}
C -- No --> D[Store project settings]
C -- Yes --> E[Test directory connection]
E --> F{Directory accepts configuration?}
F -- No --> X[Reject change]
F -- Yes --> D
D --> G[Use directory for project sign-in]
A --> H[Optional LDAP test]
H --> I[Check service account or user access]
References: src/…/Update.php• L49-79 src/…/Update.php• L118-212 src/…/Create.php• L31-80 src/…/Update.php• L68-95
Project configuration
Project configuration gives administrators control over service behavior without changing the project identity or data boundary. Custom SMTP settings are checked when custom delivery is enabled, secret values are write-only, and variable changes make affected functions and sites require a new live state. src/…/Update.php and src/…/Update.php.
Labels replace the project’s current label set after duplicate values are removed. This makes labels a project classification tool rather than a resource attached to one service. src/…/Update.php.
References: src/…/Update.php• L102-180 src/…/Update.php• L75-117 src/…/Update.php• L64-76
Project API keys
Project API keys provide controlled access to project services. The organization project-key API manages keys for a project after it confirms that the project belongs to the active organization team. A standard key has named scopes and an optional expiration. An ephemeral key provides a short-lived alternative for temporary work. src/…/Action.php, src/…/Create.php, and src/…/Create.php.
The organization API supports standard key creation, inspection, listing, and updates. Key reads and lists filter by the resolved project, so a project cannot reach a sibling project’s key in the same organization. Secret values are returned only to callers that could create the key; JWT-backed requests do not receive them. Standard key changes clear the cached project record and emit key events. src/…/Get.php, src/…/XList.php, and src/…/Update.php.
Key creation and update do not allow a caller to grant broader scopes or a later expiration than its own key permits. Ephemeral keys use a generated short lifetime and are not handled as standard persistent keys. src/…/Create.php and src/…/Create.php.
References: src/…/Action.php• L14-34 src/…/Create.php• L100-149 src/…/Create.php• L91-136 src/…/Get.php• L71-89 src/…/Update.php• L96-137 src/…/XList.php• L83-146
OAuth2 provider settings
Project OAuth2 settings connect external identity providers to project sign-in. The shared provider contract describes each provider’s identity, credentials, response shape, and any extra fields such as authorization prompts. Public provider metadata lets clients present the right setup fields to a project owner. src/…/Base.php.
The update flow keeps browser sign-in and native sign-in as separate controls. Browser sign-in needs usable credentials and checks them when the owner enables the provider. Native sign-in trusts ID tokens only when their audience matches the configured client ID or an allowed native client ID. Google adds prompt settings. Apple uses a service ID and the parts of its signing key instead of one client secret. src/…/Base.php, src/…/Update.php, and src/…/Update.php.
The provider read flow accepts only providers enabled by the server and registered with the project OAuth2 actions. It resolves the provider-specific response model through that action and returns public settings while keeping credentials write-only. Webflow follows the standard client ID and client secret setup through this same provider contract. Vipps MobilePay Sandbox has its own provider ID and update action while reusing the Vipps credential contract. src/…/Get.php, src/…/Update.php, and src/…/Update.php.
The provider registry also supports Instagram, Netlify, Patreon, Railway, Strava, and VK. Each provider uses the shared client ID and client secret setup while supplying its own identity, authentication client, SDK method, and response model. The read endpoint exposes these providers through the same provider-specific response path. src/…/Base.php, src/…/Get.php, src/…/Update.php, src/…/Update.php, src/…/Update.php, src/…/Update.php, src/…/Update.php, and src/…/Update.php.
This diagram shows how a provider setting change is checked before it becomes part of the project’s authentication settings.
flowchart LR
A[Provider settings] --> B{Browser sign-in enabled?}
B -- Yes --> C[Check browser credentials]
B -- No --> D[Keep browser state]
A --> E{Native sign-in enabled?}
E -- Yes --> F[Require a trusted token audience]
E -- No --> G[Keep native state]
C --> H[Save project OAuth2 settings]
D --> H
F --> H
G --> H
H --> I[Return non-secret provider settings]
References: src/…/Base.php• L159-205 src/…/Base.php• L302-438 src/…/Base.php• L503-591 src/…/Get.php• L26-130 src/…/Update.php• L9-55 src/…/Update.php• L8-29 src/…/Update.php• L71-120 src/…/Update.php• L76-145 src/…/Update.php• L9-55 src/…/Update.php• L9-55 src/…/Update.php• L9-55 src/…/Update.php• L9-55 src/…/Update.php• L9-55 src/…/Update.php• L9-55
Authentication policies
Authentication policies define project rules for account, password, session, membership, multi-factor, and account-device behavior. The policy list and single-policy read expose the current values from the project’s authentication settings. src/…/XList.php and src/…/Get.php.
The four email policies apply to new sign-ups and email updates. An administrator can enable each policy through its policy endpoint. The plan must support the related email validation feature before an enable action succeeds. The update writes the setting as one project change and emits a policy event. src/…/Update.php, src/…/Update.php, src/…/Update.php, and src/…/Update.php.
The account-devices policy controls whether a browser can create an account device that holds multiple sessions and can switch between them. When disabled, new account devices cannot be created, so each browser is limited to one active session. The update stores the setting in the project authentication settings, clears the project cache, and emits a policy event. src/…/Update.php.
References: src/…/XList.php• L93-200 src/…/Get.php• L75-99 src/…/Get.php• L221-270 src/…/Update.php• L67-95 src/…/Update.php• L66-94 src/…/Update.php• L21-85
Onboarding stages
Onboarding stages are project milestones tied to SDK method keys. A successful call to a configured method records a completed stage after the request ends. The record includes its status, time, and actor type so progress can show whether an administrator, user, guest, or key caused the change. The configured methods cover first-use actions across project connection, authentication, databases, storage, functions, messaging, and sites. app/…/onboarding.php and app/…/api.php.
Administrators can list all configured stages. Each stage is pending until it is completed or skipped. The stage update endpoint accepts a configured SDK method key and can mark it skipped. It keeps a completed stage completed when a later skip request arrives. src/…/XList.php and src/…/Update.php.
Stage progress is stored as JSON on the platform project record. The project collection defines this value as an optional field. A missing field remains compatible with older project records. app/…/platform.php and src/…/Project.php.
This diagram shows how normal project use and an administrator action update the same stage record.
flowchart LR
A[Successful configured SDK call] --> B[Request shutdown]
B --> C[Record completed stage]
D[Administrator skips stage] --> E[Validate SDK method key]
E --> F[Record skipped stage]
C --> G[Project onboarding progress]
F --> G
G --> H[List or update stage response]
References: app/…/onboarding.php• L4-80 app/…/api.php• L1182-1268 src/…/XList.php• L53-94 src/…/Update.php• L65-147 app/…/platform.php• L346-355
Project access context
Every project request must resolve the project named by its request context. When a project ID appears in the path, the request layer checks it against the project header and the loaded project. A mismatch is rejected before the operation runs. app/…/api.php.
Console requests use platform data and keep the authorization checks for project administration. Requests for resources inside a normal project use that project’s access rules. This separates project management rights from access to application resources. app/…/api.php.
References: app/…/api.php• L114-127 app/…/api.php• L306-338 app/…/api.php• L378-391
Deletion flow
Deletion removes the project record first and then sends a cleanup message. A worker removes project-owned platform records, project data, files, and other stored resources. Deletion is therefore a lifecycle process rather than one database operation. src/…/Delete.php and src/…/Deletes.php.
Cleanup lifecycle
The delete request confirms that the project exists, removes its platform record, and queues a delete task. The worker uses the project ID and internal sequence to locate the project data boundary. It then cleans linked resources such as platforms, keys, webhooks, schedules, notifications, databases, and storage. src/…/Delete.php and src/…/Deletes.php.
The organization delete flow adds an ownership check. It deletes only a project owned by the active organization team. Team deletion uses the same cleanup path for each project owned by that team. src/…/Delete.php and src/…/Deletes.php.
References: src/…/Delete.php• L28-80 src/…/Delete.php• L28-91 src/…/Deletes.php• L658-676 src/…/Deletes.php• L690-817
Change checklist
When these files or sections are changed, remember to consider these:
- Keep project creation variants aligned. The general and organization flows must establish the same project defaults, team link, region choice, data-store route, and post-creation behavior.
- Keep shared and isolated data layouts aligned with
Database\\Factoryand startup metadata setup. A new project metadata collection must be available in both layouts. - Keep the project collection schema aligned with the project response model. The
onboardingJSON field must remain readable for old records and writable during both automatic completion and manual skip. - Keep onboarding method keys aligned across app/…/onboarding.php, SDK route labels, stage listing, and stage updates. A key mismatch can leave a real action pending or make a skip request invalid.
- Keep service, protocol, and authentication setting keys aligned with the response model. A key mismatch can make a changed setting appear to use its default value.
- Keep LDAP configuration and LDAP authentication state aligned. Enabling LDAP through either management path must require a usable directory configuration and must keep the project response consistent.
- Keep LDAP test behavior aligned with LDAP sign-in validation. A configuration that passes a connection test must use the same host, trust, bind, and user rules as the sign-in path.
- Keep write-only LDAP bind-password handling aligned with connection changes. A caller that cannot read the stored secret must not reuse it for a changed or less trusted directory connection.
- Keep SMTP fields, secret handling, validation, and response mapping aligned. A change in write-only behavior or enable checks can expose credentials or leave mail delivery active with incomplete settings.
- Keep project variable scope and build invalidation aligned. A variable must remain a project resource, and a changed value must not leave functions or sites using an old live configuration.
- Keep project label replacement semantics aligned with label limits and project list filtering. A change from replacement to merge can make organization views show stale classifications.
- Keep video profile parameter bounds, codec normalization, enabled-codec checks, duplicate handling, and list filtering aligned across profile creation and all later video operations.
- Keep video profile project scope and event identifiers aligned. Profile records and events must use the same project identity so media jobs cannot cross project boundaries.
- Keep project key ownership filters aligned across create, read, list, and update operations in both the project and organization APIs. A missing project resource check can expose or change a key from another project.
- Keep standard and ephemeral key scope rules aligned with the project scope configuration. The key response, cache invalidation, event data, and organization compatibility routes must continue to describe the same project key.
- Keep organization key resolution aligned with team ownership and project-scoped API-key checks. A project key must not manage a sibling project’s keys even when both projects share an organization.
- Keep key secret exposure rules aligned across single-key and list responses. JWT-backed requests and callers without sufficient key-write authority must continue to receive redacted secrets.
- Keep OAuth2 provider IDs, provider action registration, server configuration, stored setting keys, response models, and public parameter metadata aligned. Browser and native sign-in must remain independently configurable, and provider secrets must stay write-only in responses.
- Keep sandbox provider IDs and update actions distinct from their production providers while sharing the intended credential and response contract. A sandbox setting must use the sandbox authentication client and SDK method.
- Keep OAuth2 read support aligned with update support. A provider that can be configured must have a supported read model and a secret-safe response path. This includes Instagram, Netlify, Patreon, Railway, Strava, and VK.
- Keep each email policy ID aligned across the policy list, single-policy read, update route, stored
authsfield, plan capability, and event name. - Keep the account-devices policy ID aligned across the policy list, single-policy read, update route, stored
auths.accountDevicesfield, response model, and event name. Its default must remain consistent across reads and updates. - Keep team-transfer authorization and permission propagation aligned. The transfer must require owner access on both teams and update the project, linked installations, repositories, version-control comments, and project database access together.
- Keep delete-worker coverage aligned with every project-owned platform collection, project collection, storage area, and external link added to the lifecycle.
Important failure modes
| Trigger | Consequence | Guard |
|---|---|---|
| The team ID does not resolve during creation | No project record or data boundary is created | Validate the team before selecting a data store or writing the project |
The ID is console, already exists, or the region is not allowed | Creation stops with a project error | Reserve the system ID, enforce unique project IDs, and check the deployment region allow-list |
| The selected data-store layout is not prepared | The project record can exist without a usable data boundary | Keep pool selection, shared-table setup, isolated namespace creation, and metadata setup in one creation flow |
| LDAP is enabled without directory hosts or a search base | The project cannot use directory sign-in safely | Require the core LDAP connection values before enabling the auth method |
| LDAP connection details change without a new service-account password | A write-only secret could be used with a different directory or trust setting | Require the bind password again when the directory connection identity changes |
| LDAP validation cannot connect or bind to the directory | The update or enable action is rejected | Test an enabled configuration before saving it as active |
| An LDAP test runs without stored connection settings or with invalid user checks | The test cannot prove that the project can use the directory | Require the stored connection values and report the failing directory step |
| A video profile uses a disabled codec or a value outside the shared bounds | The profile cannot be used by the configured video pipeline | Load the enabled codec set and apply the shared bitrate and dimension limits before writing the profile |
| A video profile name conflicts with an existing profile | The new profile is not created | Translate the project data-store duplicate error into the profile conflict response |
| A profile list cursor names a missing profile or uses an invalid query | Profile paging fails instead of returning an unsafe or incomplete result | Validate queries and cursor documents before applying project-scoped filters |
| An organization key request names a project outside the active team | The request could cross the organization project boundary | Resolve the project first and require its team identity to match the active organization team |
| A project key is read or listed without its project ownership filter | One project can access or change another project’s key | Match the key resource type and internal project identity on every organization key operation |
| A caller uses a project-scoped key against another project’s organization key route | A valid key can be used outside its project boundary | Reject mismatched project IDs unless the key explicitly has project checking disabled |
| An ephemeral key is treated as a standard stored key | Temporary access can receive the wrong lifetime or management behavior | Keep ephemeral duration and token rules separate from standard key persistence and updates |
| A caller with insufficient authority receives a key secret | Project credentials can be exposed to callers that cannot create the key | Redact secrets unless the caller has the required key-write scope and grant; always redact them for JWT requests |
| OAuth2 provider configuration is missing from server support or the provider registry | The provider cannot be read or managed through the project API | Keep server provider configuration, provider action registration, route models, and provider IDs aligned |
| A new OAuth2 provider has no matching response model or read dispatch entry | The provider can be configured but cannot be read through the project API | Register the provider action and response model together with its server provider ID |
| A sandbox OAuth2 provider is mapped to its production action or client | Sandbox sign-in can use the wrong endpoint or appear under the wrong project setting | Keep the sandbox provider ID, action, SDK method, and sandbox authentication class mapped together |
| OAuth2 browser credentials are incomplete or invalid when enabled | Browser sign-in cannot create new sessions | Require complete credentials and validate them on explicit browser enable |
| Native OAuth2 sign-in has no trusted client ID | Device ID tokens cannot be matched safely to the project | Require the provider client ID or at least one allowed native client ID before native enable |
| A provider secret is returned in a read response | Project credentials can be exposed to callers | Build read responses with secret fields cleared and accept secrets only through updates |
| Custom SMTP is enabled without a usable host, port, sender, or working connection | Project email delivery fails or uses an invalid provider | Require the core fields and validate the provider when custom delivery is enabled |
| A project variable changes without invalidating live functions or sites | Builds and runtime jobs can continue to use an old value | Mark affected resources not live after a variable change |
| An email policy is enabled on a plan without its capability | The requested sign-up rule is not applied | Check the matching plan capability before saving the enabled state |
| A policy is added to only one read or write surface | Clients can see a policy that they cannot update or cannot read | Keep policy IDs and stored authentication fields aligned across list, get, and update |
| The account-devices policy is absent from one policy surface or uses a different default | Clients can show the wrong session model or cannot change the project setting | Keep account-devices, auths.accountDevices, its response model, and the update event aligned across list, get, and update |
The onboarding field is absent or has the wrong shape | Stage progress can appear pending or an update can fail to persist | Treat missing values as empty state and keep the field as writable JSON |
| A stage key is not in the configured onboarding set | The stage cannot be listed or skipped | Use the same SDK method key in route configuration and stage management |
| A project ID in the path differs from the project header or loaded context | The request is rejected instead of changing another project | Validate all project context sources before project work starts |
| The delete message is not processed | The project record is gone but project-owned data or files can remain | Monitor the delete queue and worker cleanup for the project ID |
| A team transfer is requested by a non-owner of either team | The project could move without approval from the current or destination owner | Require confirmed owner membership in both teams before changing project ownership |
| Team transfer omits a linked platform resource or project database access update | The project and its linked resource can have different access owners | Propagate the new permissions to linked version-control resources and grant access to the project database |
Key files
| File | Why to read it |
|---|---|
| src/…/Create.php | Main project creation flow, defaults, region choice, and resource setup |
| src/…/Create.php | Organization-owned project creation variant |
| src/…/Factory.php | Project data routing for shared tenants and isolated namespaces |
| app/http.php | Server startup setup for shared project metadata collections |
| app/…/projects.php | Metadata definitions for project-owned resources |
| src/…/Update.php | Project metadata management |
| src/…/Update.php | Team transfer authorization and linked-resource permission refresh |
| src/…/Update.php | Optional service enable and disable flow |
| src/…/Update.php | Project authentication method state changes and LDAP enable guard |
| src/…/Update.php | Project LDAP settings, validation, and directory enable flow |
| src/…/Create.php | LDAP connection and optional user access test |
| src/…/Update.php | Custom project email delivery settings and validation |
| src/…/Update.php | Project variable scope and live resource invalidation |
| src/…/Update.php | Project label replacement and organization filtering metadata |
| src/…/Project.php | Project settings and onboarding progress as presented to callers |
| src/…/Create.php | Project video profile creation and codec validation |
| src/…/XList.php | Project video profile filtering and cursor listing |
| src/…/Base.php | Shared video codec rules and profile parameter bounds |
| src/…/Action.php | Organization project ownership and project-scoped key resolution |
| src/…/Create.php | Standard organization project-key creation and scope contract |
| src/…/Create.php | Short-lived organization project-key flow |
| src/…/Get.php | Organization project-key lookup and secret redaction |
| src/…/Update.php | Organization project-key updates and scope checks |
| src/…/XList.php | Organization project-key ownership filtering and list behavior |
| src/…/Create.php | Standard project key creation and scope contract |
| src/…/Create.php | Short-lived project key flow |
| src/…/XList.php | Project key ownership filtering and list behavior |
| src/…/Base.php | Shared OAuth2 settings, provider metadata, validation, dispatch, persistence, and secret-safe responses |
| src/…/Update.php | Sandbox Vipps MobilePay provider identity and production-independent OAuth2 action |
| src/…/Get.php | Enabled-provider support checks and secret-safe read response dispatch |
| src/…/Update.php | Webflow provider identity and standard credential contract |
| src/…/Update.php | Google browser and native sign-in settings |
| src/…/Update.php | Apple credentials and native client settings |
| src/…/Update.php, src/…/Update.php, src/…/Update.php, src/…/Update.php, src/…/Update.php, src/…/Update.php | Standard provider identity and credential mappings for the added OAuth2 providers |
| src/…/XList.php | Project policy catalog and current values |
| src/…/Get.php | Single-policy lookup and response mapping |
| src/…/Update.php | Account-device policy update and project authentication setting change |
| src/…/Update.php | Plan-gated email policy update pattern |
| app/…/onboarding.php | Configured SDK methods that define onboarding stages |
| src/…/Update.php | Manual stage skip and stage status response |
| app/…/api.php | Automatic stage completion and project context checks |
| src/…/Delete.php | Project deletion request and cleanup handoff |
| src/…/Deletes.php | Asynchronous cleanup of project-owned resources |