Project settings

Choose Settings → General in the Pods sidebar for the project's settings. Its sections are Project, Throttling, Logs & Retention and Routing. Change what you need, then choose Save Changes at the top. Only Owners and Admins can save; others see the settings read-only.

Project shows the Geiger project behind Pods: its name, slug, Project ID, Organization ID, status and your Inherited role. The project and its members are managed in Dash: Manage in Geiger opens your organization there.

Two sections of Settings → General set limits for the whole project.

• Throttling → Account throttle: Throttle rate (requests per second across the project) and Throttle burst (requests allowed over the rate in a short spike), 10,000 and 5,000 to start with. Every stage and usage plan limit sits under them.
• Throttling → Limit store outage: what the gateway does if it can't reach the store that counts requests. Fail open (allow traffic), the default, keeps traffic flowing unthrottled; Fail closed (reject traffic) rejects requests until the store is back.
• Logs & Retention: Log retention (days), how long access and execution logs are kept, from 1 to 3650 (30 to start with), and Full-payload trace retention (days), how long request and response bodies are kept, from 1 to 30 (3 to start with).

Access tokens let scripts and tools act on the project through Pods' API, with Authorization: Bearer and the token. Choose Settings → Access Tokens, then New Token. Only Owners and Admins can manage tokens.

• Name: up to 128 characters.
• Kind: Personal tokens act as you, with your current permissions or a subset of them, and need an Expires on date within a year. Service tokens carry exactly the scopes you pick, never more than you hold yourself.
• Scopes: permissions grouped as APIs, Build, Release, Consumers, Security and Operations. Leave them empty on a personal token to use all your permissions.

Choose Create Token. The token's value is shown once, so copy it before you close the dialog. The list shows each token's kind, scopes, status (Active, Expired or Revoked), when it was last used and when it expires. To stop a token working, choose Revoke in its ⋯ menu and confirm. Anything still using it stops working at once, and it can't be undone.

A stack describes some of the project's APIs as a JSON file, so the same configuration can be checked and applied in one step. Choose Settings → Stacks.

1. Type the Stack name. It must match the stack named inside the file.
2. Paste the file into Definition, starting from {"version":1,"stack":"payments","apis":[]}. Secret values aren't accepted in it.
3. Choose Plan to preview the changes: each resource with its kind and whether it would be created, updated or deleted, in the order apply runs them.
4. Choose Apply to make the changes.

Check Drift compares live resources with the file and shows In sync or Drift detected, with when it was last applied. Deletes are skipped when you apply from this screen. Planning and applying need the Create APIs permission, which Owners and Admins have.

The audit log records every management change in the project, newest first, with sensitive values redacted. Choose Settings → Audit Log. Everyone on the project can read it.

Each entry shows the event, the resource type, who made it, the API it touched and when. Narrow the list with Time range (All Time, Last 24 Hours, Last 7 Days, Last 30 Days or Custom Range) and Resource type, or search by action, resource or actor. Filters adds exact-match filters on Actor ID, Action (such as deployment.create), Resource type, Resource ID, API ID and a date range.

Click an entry, or choose View details in its ⋯ menu, to see its details and the values Before and After the change. The list loads 100 entries at a time; choose Load Older Entries for more. Export CSV downloads the entries, with the same filters.