Skip to content

Upstream project administration

What a project's overview, audit log, settings and members use, captured on 2026-10-23 on one project with three members. The requests follow the common shape and the identifiers of the upstream reference. Values are scrubbed as there.

Changing a member's role was captured. Every other write on this page was read from the page's script (paas_master.paas_app_assets), not captured: saving settings, adding and removing a member.

Access

The page shows the project's Audit Logs and Settings to an admin only, and its Branches, Builds and Status to a developer and above. Levels are those of access_level_map in the config of get_info (project_info.json). What upstream answers a user below them was not seen.

Overview

No request is a project overview. The project's Status page (POST /app/project/<technical_name>/status, read from the script) is the platform's own: each server's roles, whether they are online, and probe percentages. It says nothing about the project.

The figures of an overview are in the repository of the project's settings. Sizes are in KiB.

Figure Fields Also in
Subscription subscription_validity (valid), subscription_code, subscription_recurrence (1), subscription_next_invoice (a date) subscription_validity and subscription_code in get_info; subscription_validity in projects
What it pays for subscription_workers, subscription_stagings, subscription_storage, subscription_dedicated
Odoo version odoo_branch (19.0) projects, get_info
Region geolocation (eu), hosting_location and hosting_location_dev (Europe) projects gives geolocation as Europe
Storage used_storage, max_storage (1048576, one GiB), max_GB, production_build_size, size_staging, size_others
Workers max_production_workers, max_staging_branches, pays_dedicated pays_dedicated in get_info

production_build of the same answer splits the production size into size_container, size_database, size_custom_branch and size_total, with its worker_url and branch_id.

Client.project_overview reads what the project page and its Settings page send, read from the script on 2026-10-24 from the capture of 2026-10-23: the project page asks get_info then branches, the Settings page get_info then get_settings. The region comes from projects, which answers it to every member.

Request Read
get_info active_repo: id, owner, name, project_name, technical_name, subscription_validity, odoo_branch, pays_dedicated, production_expiration_days_left (null seen), production_build_id (id, branch_name, url, or false); user.access; config.access_level_map
projects The listed project's geolocation (Europe)
branches Each branch's stage, last_build_id, last_build_status and last_build_result
get_settings repository: used_storage, max_storage, max_production_workers, max_staging_branches
  • The page shows Settings when access_level_map[user.access] >= access_level_map["admin"]. The library applies the same test before asking get_settings.
  • subscription_validity: valid was seen. The templates also name trial ("Trial"), custom ("Non-standard") and invalid ("Expired"). The project page shows "Invalid Subscription" for any other value.
  • The page's "Total accounted storage" is production_build.size_total * 4 + size_staging, which equalled used_storage in the one capture. used_storage is also the least the storage input accepts.
  • production_expiration_days_left is the days left of a trial given by a partnership code.
  • get_info holds access_token, subscription_code and the production build's enterprise_code (only false seen). projects holds each project's subscription_code. get_settings holds ci_token, the GitHub token for commit statuses (only false seen; the page tests it for truth only), subscription_code, subscription_code_display and upsells.accounts_link, whose contract is the subscription code. The library drops them before reading.

Audit log

POST /app/project/<technical_name>/audit_logs, no params. Fixture: audit_logs.json.

result is a list, newest first, with no paging: 47 entries going back 25 days. The page says it shows the last 30 days.

Field Type Observed
date str UTC
action str Allow IP, Connect as user, Download database, Manage collaborators, Open Editor, Open Shell, Open Webmail, Open database logs
stage str production, staging, dev, or empty for a project action
user str The GitHub login of who did it
message str Free text, often empty; holds IP addresses, logins and SSH client versions
successful bool true; the page shows it only when the project is_staff_restricted
  • A role change is logged as "Change access rights of user <login> from <old> to <new>".
  • The page asks once, in onWillStart, and its SearchTable pages the rows itself, 25 a screen, sorted by date descending.
  • The CSV export also holds Change branch stage, Add domain name and Manage settings, which the 30 days of JSON did not.
  • GET .../audit_logs/download/csv and .../download/xls give up to a year, as attachments named audit_log_<project_name>. The CSV columns are Date, Github User, Repository (<owner>/<name>), Stage, Database, Action and Extra Information. Its dates were two hours ahead of the JSON's, which matches the zone of the tz cookie.

Seen once.

Client.audit_log asks get_info, applies the page's admin test to it, then asks audit_logs once and reads every field above but none of the exports. It sorts the entries by date itself, as the page does.

Project settings

POST /app/project/<technical_name>/get_settings, no params. Fixture: project_settings.json, which leaves out the upsell links and the limits' descriptions.

Key of result Holds
repository The settings, and the overview figures
users The members
production_build Its sizes, above
submodules Private submodules: id, name, deploy_key_public, deploy_key_public_fingerprint. Empty here
dedicated_limits limit_real_time and limit_real_time_cron, each with value in minutes and bounds in seconds
session_lifetime, session_lifetime_map auto, and the choices from 4-hours to 8-days with their seconds
domain_build_production, title, dedicated
upsells can_have_worker_upsell_trial, and accounts_link, an odoo.com link to manage the subscription whose contract query value is the subscription code

The other settings in repository are the development defaults (modules_auto, modules, test_mode, test_tags, demo_data, ai_agent, as on a branch), disable_tests, private, block_odoo_domain, deploy_key_writable, ip_whitelist, ci_token, ci_suspended and project_name.

  • session_lifetime and session_lifetime_map are keys of result, not of repository. The page copies them into its settings.
  • A submodule's name is the Git URL the user typed, sent back as submodule_name. The page shows deploy_key_public in a read-only input with a copy button.
  • No template or script reads disable_tests.
  • private is the opposite of the page's "Allow public access", which it sends as public.
  • ci_suspended is also set by the page from check_ci_token: true when the token's check failed.
  • The Workers Settings inputs, the two dedicated_limits, are disabled unless pays_dedicated.

Client.project_settings asks get_info, applies the page's admin test to it, then asks get_settings, the request the overview shares. It drops ci_token, subscription_code, subscription_code_display and upsells whole, and a submodule URL's query, fragment and user information but a lone SSH user name, or the whole URL when it cannot be read safely, before reading.

Field Read from
name repository.project_name, which must be the name asked
odoo_domain_blocked repository.block_odoo_domain
session_lifetime session_lifetime, one of the seven keys of session_lifetime_map seen; the map is read only to change it
public Not repository.private
commit_statuses_suspended repository.ci_suspended
deploy_key_writable repository.deploy_key_writable
submodules submodules: id, name, deploy_key_public_fingerprint and deploy_key_public, which must be an OpenSSH public key line, a trailing line break removed. Never seen filled
hosting repository, as in the overview
dedicated repository.pays_dedicated
http_timeout_seconds, cron_timeout_seconds value × unit_conversion of dedicated_limits.limit_real_time and limit_real_time_cron
module_install to ai_agent repository.modules_auto, modules, test_mode, test_tags, demo_data, ai_agent, as on a branch
ip_allow_list repository.ip_whitelist, split into lines, blank ones skipped, each a network when it holds a / and an address otherwise: what set_settings accepts beyond the IPv4s the page asks for is unseen

POST /app/project/<technical_name>/set_settings, read from the script (SettingsPage.saveSettings), not captured. As on a branch, its params are one section of the page as form values, a checkbox as "on" or "off". The page merges its result into what it holds and looks for a saved field in it, so it holds what was saved, not the whole repository.

Section Params Touches access
Project name project_name, block_odoo_domain No
Session lifetime session_lifetime, a slider's position in session_lifetime_map ("0" is auto) Yes: how long any member's session lasts on the project
Public access public Yes: opens the Builds page and the development builds to anyone
GitHub commit statuses ci_token or reset_ci_token A GitHub token
GitHub key and webhook deploy_key_writable with a hidden redeploy_key of 1, or redeploy_webhook Yes: the deploy key's write access to the repository
Production database size max_storage No; billed
Database workers max_production_workers, pays_dedicated No; billed
Workers settings limit_real_time, limit_real_time_cron, in the limit's unit No
Staging branches max_staging_branches No; billed
Development branches The development defaults, the whole section on any change, rendered as on a branch No
Firewall ip_whitelist Yes: SSH, and PostgreSQL on a dedicated server, to production and staging
Activation subscription_code No; billed
  • ip_whitelist is IPv4 addresses, one per line, at most 10, applied within 5 minutes.
  • A result with new_sub_values is a subscription change waiting for confirmation, which the page asks for and then sends again with code_upsell_confirm. The page also confirms a raise of a billed field before sending.
  • Collaborators, submodules (create_submodule_deploy_key), and the limits' reset_default_limits have requests of their own.
  • A change of block_odoo_domain is answered "job_queued". Every save of the GitHub key section sends redeploy_key, which deploys the key again on GitHub.
  • The slider's position is an index into Object.keys(session_lifetime_map), sent as a string. A limit's input takes value in its unit, between min and max divided by unit_conversion and rounded down, and only while pays_dedicated.

The library sends, in one request, the fields it is given that differ from get_settings, and reads the settings again rather than result, as on a branch. set_project_settings.json stands for the answer. It sends:

Field Sent as
session_lifetime The index of its key in session_lifetime_map as answered, which must hold the seven keys seen
public public, "on" or "off"
http_timeout_seconds, cron_timeout_seconds limit_real_time and limit_real_time_cron both, as the page sends its section: the seconds given divided by unit_conversion, which must divide them, within the input's bounds, and the other at its value as read, on a project that pays_dedicated
module_install to ai_agent As on a branch, and refused as the page would not render them
allow_ips, disallow_ips ip_whitelist: each line of the text read in the same call kept as written, those whose entry is removed left out, then each address added. At most 10 entries. An edit made elsewhere between the read and the write is overwritten, as by the page
  • That a field sent alone, or with fields of other sections, leaves the others as they were is inferred, as on a branch: the firewall, public access and session lifetime sections hold one field each, but the development section is sent whole. The settings read back are compared with those before, the ones the library does not send included, so a reset is reported.
  • The project name, block_odoo_domain, the deploy key, the commit-status token, submodules and the billed fields are not sent by the library.

Members

The members are users of get_settings, which the Settings page lists in its Collaborators item (paas_master.GithubUserManager), so to an admin only. Fixture: project_settings.json.

Field Type Observed
id int The membership: what a role change and a removal name
username, name str The GitHub login, twice
hosting_identifier str The GitHub user id
avatar_url str
access_level str admin for all three
user_id [id, name] or false false shows "Pending login" (script)
hosting_user_id [id, name] Named as the hosting_user_id of Projects; the two were not compared

Roles, lowest first, from access_level_map: developer (100), tester (200), admin (300). Each member's select lists the keys of access_level_map but its empty one. No member carries an email: the only one in these answers is the session user's own, in get_info.

Client.members asks get_info, applies the page's admin test to it, then asks get_settings with the drops of Project settings. It reads id, username, name, hosting_identifier (ASCII digits, or a changed shape), access_level (a role it does not know is a changed shape) and whether user_id is false. It leaves avatar_url unread, as a URL handed to an agent is one it may fetch, the pair of user_id, which is Odoo.sh's own user and repeats the login, and hosting_user_id, which only a removal takes.

POST /app/user_access/<id>/set_access_level, params {"access_level": "<role>"}. Fixture: set_access_level.json. The answer has no result key, as a rebuild. Captured on one member, from admin to tester, developer and back to admin, and each change was in the audit log.

Adding a member, read from the script apart from the search:

  1. POST /app/github/find_users, params {"query": "<text>"}, searches GitHub as the user types. result is GitHub's own user objects (login, id, avatar_url, html_url, name, ...).
  2. POST /app/github/get_user_profile, params {"github_username": "<login>"}.
  3. POST /app/project/<technical_name>/add_collaborator, params github_username, access_level (the page offers developer, the default, tester and admin) and send_invitation. Its result is the new member, which the page adds to users.

A new member is named by their GitHub login.

find_users needs Odoo.sh's GitHub grant to have the repo scope, beyond the read:user user:email of login. Without it the answer is InsufficientScopeError (fixture insufficient_scope.json), whose arguments hold a GitHub authorize URL asking for read:user user:email repo. Following it ran the login's hops again and set a new session_id.

Client.add_member asks get_info with the admin test, then get_settings, and refuses a login already listed, in any case. It then asks find_users with query set to the login, reading only login, id and type of each item. It takes the item whose login is the one given in any case and is itself a GitHub login, as the page's Enter takes users[0] only when its login is the query, and whose type is User, as the search finds organisations too. None is NotFoundError, and an id already a member's hosting_identifier is refused. It sends add_collaborator once with the login as GitHub spells it, the role, and send_invitation false: the page's dialog starts with false and has no control for it. It does not read the result: the new member is the one get_settings lists, read again, with that hosting_identifier and role. InsufficientScopeError is PermissionDeniedError, which for find_users names the page's search as where to give the grant; its URL is not read.

Client.set_member_role asks get_info with the admin test, keeping user.username, then get_settings, and sends set_access_level once on the listed id, or nothing when the member has the role. The page tests nothing before a role change; the library refuses lowering an admin when no other admin with a user_id remains, as an invitee who never logs in administers nothing. It reads the role back from get_settings, or, when the member is the session's user, from get_info's user.access, since get_settings is an admin's only. The revoke dialog warns that a removal fails for the last administrator of a project; what upstream does on a last-admin demotion was not seen.

Removing a member: POST /app/user/<hosting_user_id>/revokable_count gives how many of the user's projects they can be removed from, and POST /app/user_access/<id>/revoke, params {"all_projects": <bool>}, removes them. Its result is true when the user removed themselves.

Not seen

  • A settings save, an added or removed member, and their answers: add_collaborator.json stands for the answer to an addition, built from the script.
  • What upstream answers a change that lowers the last admin of a project.
  • The project Status answer.
  • What a member below admin gets from these requests.