Chelabase
ManagementApp users

Disable app users

DELETE
/v1/projects/{id}/app-users

Refused while the project's pool has any user. Otherwise 202: the worker removes the guard machinery (the table stays as an ordinary table), drops the pool and deletes the settings. Pressing it again while disabling starts the work again.

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Project id

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/app-users"
{  "database_id": "91088904-0b92-46ad-9240-e1afa0da22df",  "email_verification": true,  "error": "string",  "on_delete": "delete",  "pg_database": "string",  "schema": "string",  "status": "enabling",  "table": "string"}

Get a project's app-users settings GET

Previous Page

Enable app users, or change their settings PUT

With no settings yet this enables app users: it checks the database, the data API on every branch and the table, then answers 202 and the worker creates the project's identity pool, the users table and its guard. Pressing it again while `enabling`, or after `failed` (same location), starts the work again (202), and so does pressing it on a disable on hold (`disabling` with an `error`: its pool still has users), which keeps the pool and its users. Once enabled it changes `email_verification` and `on_delete` only (200); another location is 409 `app_users_location_fixed`.