slug: accela provider: Accela generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Public Sector & Government - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 12 edges: - tag: Inspections spec_file: accela-inspections-api-openapi.yml capability_id: BC-3240.40 capability_id_l1: BC-3240 capability_name: Inspection and Compliance Verification confidence: 0.92 evidence: POST /v4/inspections/schedule 'Schedule Inspection'; PUT /v4/inspections/{id}/result 'Result Inspection'; description 'manage inspection records during their complete lifecycle from application submittal to permit issuance or license issuance' reason: Scheduling, assigning, resulting and cancelling agency inspections tied to permits and licences is squarely Inspection and Compliance Verification. - tag: Inspections/Checklists spec_file: accela-inspections-checklists-api-openapi.yml capability_id: BC-3240.40 capability_id_l1: BC-3240 capability_name: Inspection and Compliance Verification confidence: 0.85 evidence: '"Get All Checklists for Inspection", "Create Inspection Checklist"; inpsectionChecklistModel' reason: Checklists used to conduct agency inspections against permit/licence conditions; part of the inspection and compliance verification capability. - tag: Inspections/Checklists/Checklist Items spec_file: accela-inspections-checklists-checklist-items-api-openapi.yml capability_id: BC-3240.40 capability_id_l1: BC-3240 capability_name: Inspection and Compliance Verification confidence: 0.85 evidence: '"Get All Inspection Checklist Items", "Update Checklist Items", "Get All Inspection Checklist Item Statuses"' reason: Item-level recording of inspection findings and statuses with supporting documents — the execution detail of government inspection and compliance verification. - tag: Records/Inspections spec_file: accela-records-inspections-api-openapi.yml capability_id: BC-3240.40 capability_id_l1: BC-3240 capability_name: Inspection and Compliance Verification confidence: 0.85 evidence: GET /v4/records/{recordId}/inspections 'Get All Inspections for Record'; 'Get All Inspection Types for Record'; schemas inspectionModel, inspectionTypeModel, rGuideSheetGroupModel reason: Exposes inspections and inspection types tied to permit/licence records on a govtech permitting platform — directly the inspection and compliance verification step of permit administration. - tag: Citizen Access Self-Registration spec_file: accela-citizen-access-self-registration-api-openapi.yml capability_id: BC-3220.20 capability_id_l1: BC-3220 capability_name: Citizen Identity & Authentication confidence: 0.8 evidence: POST /v4/citizenaccess/register Register Citizen; Get My Citizen Profile reason: Self-registration and profile establishment of citizen users for agency online services (publicUserRegisterModel, citizenProfileModel, publicUserQuestionModel). This is establishment of citizen digital identity/credentials for government service access. - tag: Citizen Access User Management spec_file: accela-citizen-access-user-management-api-openapi.yml capability_id: BC-3220.20 capability_id_l1: BC-3220 capability_name: Citizen Identity & Authentication confidence: 0.8 evidence: Create Citizen User / Update Citizen Profile / Update Citizen Account Status / Update Citizen Password reason: Agency-side administration of citizen portal accounts, profiles, credentials and account status for access to government services — citizen identity and authentication management rather than generic enterprise IAM, as the subjects are citizens of an agency. - tag: CivicId spec_file: accela-civicid-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.78 evidence: '"Civic ID is a userid that allows a user to login multiple Accela products ... it allows a user to link multiple agency Citizen Access accounts to a single login account"; GET /v4/civicid/accounts Get All Linked User Accounts' reason: A single-sign-on identity that links multiple agency accounts to one login, with operations to create, read and delete linked accounts and read the identity profile. This is identity federation / account linking, i.e. Identity & Access Management. - tag: CivicId spec_file: accela-civicid-api-openapi.yml capability_id: BC-3220.20 capability_id_l1: BC-3220 capability_name: Citizen Identity & Authentication confidence: 0.78 evidence: '"Civic ID is agency agnostic; it allows a user to link multiple agency Citizen Access accounts to a single login account"; Get All Linked User Accounts' reason: A federated citizen login identity linking accounts across government agencies — squarely citizen identity and authentication for government service access, not generic workforce IAM. - tag: Inspections/Condition Approvals spec_file: accela-inspections-condition-approvals-api-openapi.yml capability_id: BC-3240.40 capability_id_l1: BC-3240 capability_name: Inspection and Compliance Verification confidence: 0.78 evidence: '"Create Inspection Approval Conditions"; schema inspectionConditionModel' reason: Manages approval conditions recorded against government inspections in a permitting/licensing platform — inspection and compliance verification against permit conditions. - tag: Inspections/Conditions spec_file: accela-inspections-conditions-api-openapi.yml capability_id: BC-3240.40 capability_id_l1: BC-3240 capability_name: Inspection and Compliance Verification confidence: 0.78 evidence: '"Get All Standard Conditions for Inspection"; "Get Inspection Condition History"' reason: Standard conditions attached to agency inspection records on permits/licences — directly the inspection and compliance verification capability. - tag: Records spec_file: accela-records-api-openapi.yml capability_id: BC-3240 capability_id_l1: BC-3240 capability_name: Permits, Licences & Authorisations Management confidence: 0.7 evidence: '"Create Record", "Create Partial Record", "Finalize Record"; vendor platform "runs permitting, planning, licensing, code enforcement, inspections"' reason: Records are the core permit/licence/application objects of Accela's government platform, so the lifecycle operations realise permits, licences and authorisations management; record types span permits, enforcement and service requests so no single L2 is safe. - tag: Records/Invoices spec_file: accela-records-invoices-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.7 evidence: '"Get All Record Invoices", "Create Record Invoices"; schemas invoiceModel, feeItemModel' reason: Creating and retrieving invoices from fee items against a record is customer invoicing, the core of Accounts Receivable Management. Confidence moderate because only invoice creation/read is exposed — no collections or cash application.