Accela · OAuth Scopes
Accela OAuth Scopes
OAuth 2.0
searched
Accela publishes 32 OAuth 2.0 scopes via the authorization_code, implicit, and password flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Accela API on a user’s behalf.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
GovTechGovernmentPermittingLicensingCode EnforcementInspectionAsset ManagementCitizen EngagementLand ManagementCivic PlatformPublic SectorSoftware-as-a-Service
Scopes: 32
Flows: authorization_code, implicit, password
Method: searched
Scopes (32)
| Scope | Description | Flows |
|---|---|---|
| records | Transactional records (permits, licenses, service requests, applications) and every child resource that hangs off a record — addresses, contacts, conditions, comments, costs, fees, documents, owners, parcels, professionals, workflows and votes. | |
| inspections | Inspections, inspection scheduling and results, checklists and checklist items, inspection conditions and approvals, inspectors and inspection time accounting. | |
| contacts | Reference contacts and their addresses, conditions, custom forms and custom tables. | |
| settings | Read-only Civic Platform Administration configuration: standard choices, record/inspection/asset types, departments, priorities, statuses, pick lists and drilldowns. | |
| users | Citizen Access user accounts, self-registration, delegates and delegate privileges, and CivicID-linked citizen profiles. | |
| assets | Assets, asset attributes, linked assets, asset documents and the records attached to an asset. | |
| documents | Document metadata, upload, download and thumbnails, plus the document review surface and document settings. | |
| addresses | Reference addresses, their conditions, the parcels and records they are attached to. | |
| professionals | Licensed professionals, their conditions and the records they appear on. | |
| assessments | Condition assessments against assets — observations, attributes, documents and generated work orders. | |
| parcels | Reference parcels, their conditions, owners, addresses and records. | |
| agencies | Agency directory, agency environments, environment status and agency logo. | |
| conditions | Standard conditions and standard approval conditions defined at the agency level. | |
| civicid | CivicId accounts and profile — the cross-agency identity that links multiple agency Citizen Access accounts to one login. | |
| owners | Reference property owners and their conditions. | |
| shoppingcart | Citizen shopping carts used to assemble fees before payment. | |
| payments | Payment initialization, commit and void, and transaction fees. | |
| reports | Report definitions, report categories and report execution. | |
| timeaccounting | Time accounting entries against records and inspections. | |
| announcements | Agency announcements shown to citizens, and marking them read. | |
| app_data | App settings and Civic Platform server properties (AA version). | |
| filters | Saved filters and filter result execution. | |
| gis | Reverse geocoding and GIS dynamic themes. | |
| batch_request | The batch endpoint, which composes multiple Construct calls into one request. | |
| costs | Record cost items. | |
| global_search | The cross-object global search endpoint. | |
| invoices | Invoices attached to records. | |
| mileage | Mileage entries created by field staff. | |
| parts | The parts search endpoint. | |
| search_costs | The cost search endpoint. | |
| trustaccounts | Citizen and record trust accounts. | |
| workflows | Workflow tasks assigned to the authenticated user. |
📄 Provider scope reference: https://developer.accela.com/docs/construct-permissionScopes.htmlhttps://developer.accela.com/docs/construct-apiAuth.htmlhttps://developer.accela.com/docs/api_reference/api-index.html
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.