Saltar al contenido

Diccionario de datos

691 tablas y 261 vistas con 10789 columnas, generado a partir de los comentarios del esquema de la base de datos.

Cada tabla y columna lleva un comentario en su migración. La CI regenera esta página a partir de una base de datos recién migrada y falla cuando difiere, así que siempre coincide con el esquema. Las descripciones están en inglés, tal como las escribe el esquema.

app

Los datos de las organizaciones y de la plataforma, con seguridad a nivel de fila en cada tabla.

  • access_gridThe access grid (Section 7.4): which credential category may enter which zone, at what canon access level, during which time window.
  • access_review_campaignsAccess review campaigns (Section 8.4): reviewers confirm or remove each member's role.
  • access_review_itemsOne role assignment to confirm or remove in an access review campaign (Section 8.4).
  • access_scansAppend-only log of credential scans at zones.
  • accommodation_assignmentsRoom assignments of guests within an accommodation block.
  • accommodation_blocksHotel room blocks contracted for a project: rooms held each night between check-in and check-out, released back to the hotel on the cutoff date.
  • account_membership_rolesAccount roles held through an account membership; a member may hold several and their reach is the union (Section 4.8.1).
  • account_membershipsA person in an external organization's account (Section 4.8.1 Account Membership).
  • account_notification_defaultsA company account's notification default per category and outside channel (Section 4.5.6 company settings item 7): what its team members receive from the organizations they work with until they choose for themselves.
  • accounting_period_state_transitionsAppend-only ledger of accounting period state changes, written only by app.transition_accounting_period and period creation.
  • accounting_periodsFinancial periods of an org (Section 7.4).
  • active_org_selectionsThe org each sign-in chose in the context switcher (ADR 0007 item 1).
  • activity_eventsUser-facing activity feed (Section 7.3): one row per domain event with the person who caused it, kept 18 months in monthly partitions.
  • addon_purchasesOne-time add-ons an org paid for through Stripe Checkout, such as an Aurora request pack (ADR 0035).
  • advance_packetsAdvance packets sent to talent, vendors and venues to collect what the production needs to know.
  • advance_promotionsAppend-only links from an advance submission to the record it was promoted into.
  • advance_recipient_tokensToken links that let an advance recipient answer in Gateway without an account (Section 4.4.6).
  • advance_recipientsParties an advance packet goes to: a person or a counterparty, never a free-text address.
  • advance_sectionsSections of an advance packet.
  • advance_submissionsA recipient's answer to an advance section (rich text), with its review.
  • agency_slatesNamed staff a staffing agency puts forward on its application, one row each (Section 4.4.3).
  • agreement_state_transitionsAppend-only ledger of agreement state changes, written only by the agreement transition RPCs and creation.
  • agreementsAgreements prepared for signature (Section 7.4 People): offer letters, contractor agreements, MSAs and NDAs.
  • ai_never_sendEverything packages/ai strips before a model call: whole excluded tables (column_name null) and every Restricted column (Section 4.7).
  • ai_requestsOne row per Aurora AI model call (Section 4.7): who asked, for which feature, with which configured model, about which record, and the prompt and output with personal data redacted.
  • ai_settingsAurora AI switches, one row per org (Section 4.7).
  • ai_suggestion_fieldsProposed field values of an AI suggestion, each with a confidence score and provenance agent (rank 40, Section 3.8).
  • ai_suggestion_state_transitionsAppend-only ledger of ai suggestion state changes, written only by the ai suggestion transition RPCs and creation.
  • ai_suggestionsA change an Aurora feature proposes (Section 4.7).
  • ai_usageAurora AI metering (ADR 0020): one row per authorized request.
  • api_keysOrg-scoped API keys for servers (ADR 0003): hashed, capability-scoped and expiring.
  • application_answersAnswers to an opportunity's questions, one per question per application.
  • application_boardApplications as the Pipeline board reads them (Section 4.5.5): applicant name, shortlist rank, next interview, the offer in force and whose turn it is, and the bid total only once the bid is unsealed for the reader (Section 8.7).
  • application_state_transitionsAppend-only ledger of application state changes, written only by the application transition RPCs and creation.
  • applicationsAn application to an opportunity by a person (applying for themselves or through their representative) or an external account (a bid or an agency slate) (Section 4.4.3).
  • approval_decisionsAppend-only decisions on approval steps, written only by app.decide_approval: one per step, one step per approver, never by the requester.
  • approval_instancesA spend document going through its approval policy.
  • approval_policiesApproval policies (Section 4.10 workflow engine): ordered approval steps a spend document passes before its own approval RPC accepts it.
  • approval_policy_state_transitionsAppend-only ledger of approval policy state changes, written only by the approval policy transition RPCs and creation.
  • approval_state_transitionsAppend-only ledger of approval state changes, written only by the approval transition RPCs and creation.
  • approval_stepsOrdered steps of an approval policy.
  • asset_classesAsset classes (Section 3.9 class grain): what a kind of owned equipment is, bound to its canon element, one per element per org.
  • asset_custodyAppend-only custody ledger: each row hands an asset unit to a person or place, optionally for a project.
  • asset_damageDamage reports against an asset unit.
  • asset_identifiersIdentifiers an external authority issued for an asset unit (serial, GTIN, MPN): recorded and validated, never minted (Section 3.6).
  • asset_lot_balancesQuantity on hand per live lot: the opening count plus every ledger delta.
  • asset_lot_movementsAppend-only lot ledger: each row moves a lot quantity by a delta, for a recount, a check-out to a person or a check-in.
  • asset_lotsA quantity of an asset class at a place (Section 3.9 lot grain).
  • asset_maintenanceMaintenance performed on an asset unit.
  • asset_state_transitionsAppend-only ledger of asset state changes, written only by the asset transition RPCs and creation.
  • asset_unitsIndividual assets (Section 3.9 unit grain) tracked by asset tag, with the nine-value lifecycle.
  • attachment_versionsOne stored file per attachment version: its object in the attachments bucket, type, size, checksum and virus-scan state.
  • attachmentsFiles attached to a subject row (Section 7.3).
  • attendance_countsAttendance imported from a ticketing source (Section 17) for the gate 8 measurement: tickets sold, scanned and comped per project, show, day and ticket class.
  • audit_eventsAppend-only compliance ledger (Section 7.3, Section 8.4): who did what to which row, with a diff.
  • automation_actionsOne action of an automation, run in position order as the owner through a public API operation (ADR 0047): create_task (records.create), update_status (records.transition), assign (records.update), add_comment (comments.postOnSubject), notify (automationRuns.notify) or call_webhook (automationRuns.deliverWebhook).
  • automation_conditionsOne condition of an automation, or a group of conditions (ADR 0047).
  • automation_run_stepsOne action of an automation run (ADR 0047): the public API operation called as the owner, what was sent and answered, and how long it took.
  • automation_runsThe automation runs ledger (Section 7.3, ADR 0047): one run per automation and domain event, so an event never runs an automation twice.
  • automationsAutomations (Section 7.3, Section 4.5.6 item 20, ADR 0047): when a domain event of the trigger type happens in the org and the conditions hold, the actions run as the owner through the public API.
  • availability_blocksPeriods on an availability calendar.
  • availability_calendarsA person's availability calendar (Section 4.4.1), owned by the person.
  • background_checksBackground checks run through the provider (Checkr), which handles FCRA disclosure, authorization and adverse action (Section 4.4.4, Section 14.9).
  • beo_linesMenu and service lines of a BEO.
  • beosBanquet event orders.
  • bid_linesLines of a sealed bid.
  • bid_totalsBid totals derived from their lines, NULL-aware: a bid with an unpriced line has no total and counts its unpriced lines.
  • bidsA vendor's sealed line-item bid on a Bid opportunity, one per application (Section 4.4.3).
  • billing_checkoutsStripe Checkout sessions Atlas opened to move an org onto a paid plan (ADR 0033 decision 59).
  • billing_drawsProgress billing draws of a project, each billed through at most one receivable invoice.
  • blocksPeople and organizations a person has blocked (Section 4.5.6 Profile Privacy).
  • brand_fontsFont families a brand may choose.
  • break_glass_sessionsEmergency full access an Owner took for one hour with a second factor and a written reason (Section 8.4).
  • budget_line_amountsBudget line amounts, derived: extended amount (NULL when unpriced, never zero), contingency moved in and out, the GL account (the item's explicit default, else by class: decision D13 as owner decision 39 reads it) and approved spend.
  • budget_line_factsOne row per live budget line with both GL dimensions, the derived account, the NULL-aware extended amount and approved spend.
  • budget_linesBudget lines (Section 7.4).
  • budget_revised_totalsBudget totals with approved change orders applied.
  • budget_totalsBudget totals, NULL-aware: the total is NULL while any line is unpriced, with the unpriced count and the priced subtotal beside it (Section 3.7, invariant 11).
  • budgetsBudgets of a project.
  • calendar_exceptionsDays a calendar treats differently from its normal week, one row per day.
  • calendar_feedsiCalendar feeds of shifts, meetings, milestones and deadlines (Section 4.6.5), for one member or one of their projects.
  • calendarsWorking calendars of a project that schedules count working time against.
  • call_sheetsThe call sheet of a project day.
  • canon_extension_proposalsAn org's proposed canon extensions (Section 7.2): disciplines and categories in the adopter range .50 to .99.
  • canon_extension_state_transitionsAppend-only ledger of canon extension state changes, written only by the canon extension transition RPCs and creation.
  • capabilitiesFine-grained capability verbs (Section 8), generated from packages/schemas/capabilities.yaml.
  • capability_documentsVenue capability documents (tech packs, rigging plots) with a validity window.
  • capability_modulesModules that group capabilities, generated from packages/schemas/capabilities.yaml.
  • capability_statementsRequirements and capabilities in one shape (Section 7.4): a direction facet says whether the project requires the URID or a venue or vendor provides it, so reconciliation is a join.
  • catalog_bindingsTenant catalog items bound to canon elements (Section 7.4).
  • certification_holdersPeople holding a certification.
  • certification_sharesA person sharing one profile certification with an org, under a profile_sharing consent record (ADR 0019 carry-over).
  • certificationsCertifications an org tracks, such as rigging or first aid.
  • certified_payroll_projectsThe WH-347 header of a project covered by the Davis-Bacon and Related Acts.
  • certified_payroll_submissionsEach weekly certified payroll issued for a project.
  • change_order_line_factsOne row per live change order line with its dimensions and NULL-aware amount.
  • change_order_linesLines of a change order.
  • change_order_state_transitionsAppend-only ledger of change order state changes, written only by the change order transition RPCs and creation.
  • change_order_totalsChange order totals: NULL while any line is unpriced, never zero, with the unpriced count (invariant 11).
  • change_ordersChange orders against a budget.
  • chat_message_translationsMachine translations of chat messages (Section 4.9), one per message and reader language, cached so each is translated once.
  • chat_messagesA chat message.
  • client_approval_requestsItems the org asks its Client party to approve (Section 4.4.4 Client): a change order or a record of the engagement's project.
  • clock_punchesAppend-only record of clock punches as devices reported them (Section 13).
  • column_classificationsColumns classified Public, Confidential or Restricted, and the capability that unmasks each Restricted one (Section 8.3).
  • comment_mentionsPeople mentioned in a comment.
  • comment_reactionsOne reaction of one person to one comment.
  • comment_subjectsTables whose rows carry comments and attachments.
  • comment_threadsComment threads on any subject row (Section 7.3: one unified comment system).
  • comment_versionsEdit history of comments: the text each comment had before every edit or deletion, numbered from 1.
  • commentsComments in a thread.
  • consent_purposesProcessing purposes with their lawful basis.
  • consent_recordsConsent given by a person to an org for one purpose (Section 14.3): the notice version shown, where and when it was captured, and its withdrawal.
  • content_moderation_decisionsAppend-only decisions by an org's moderators on reported posts, comments and messages (ADR 0033 decision 57), with A90's statement of reasons in parts (1473).
  • content_reportsReports of a post, a comment on a post or a chat message to the org's moderators (ADR 0033 decision 57, App Store Review Guideline 1.2).
  • contingency_drawsAppend-only draws from a Contingency budget line to another line of the same budget.
  • conversation_membersWho takes part in a conversation, with their read position.
  • conversationsA chat conversation (Section 4.9 Chat): one-to-one between two members, or the conversation of a group.
  • cookie_consent_eventsCookie banner decisions, stored server-side as the consent log (Section 14.3 ePrivacy).
  • correction_state_transitionsAppend-only ledger of correction state changes, written only by the correction transition RPCs and creation.
  • cost_centersCost centers, GL dimension 1 (Section 3.11, Bible tab 30): CC-VENUE, CC-CORP and one per event scope.
  • counterpartiesAnother organization as this org deals with it: client, vendor, sponsor or other counterparty (Bible tab 28).
  • credential_categoriesCredential categories of a project, such as ALL-ACCESS or CREW.
  • credentialsCredentials issued to people.
  • crisis_alertsCrisis alerts announced on a project under a global canon emergency code (decision D15).
  • cue_callsDepartment calls of a cue: what audio, lighting, video, special effects and stage do on it, one row per department.
  • cuesCues in a running order.
  • currenciesISO 4217 currencies with their minor unit exponent, for rendering money stored in minor units.
  • current_legal_acceptancesThe latest accepted version of each document per person and org, for re-acceptance prompts after a material change and for Settings > Legal.
  • custom_field_choicesAllowed options of a Choice custom field.
  • custom_field_definitionsOrg-defined fields on built-in tables (Section 7.3 Workflow engine).
  • custom_field_targetsBuilt-in tables an org may add custom fields to (Section 4.5.6 org settings item 16), for the Custom Fields settings page.
  • custom_field_valuesValue of one custom field on one row of a built-in table, in the typed column of the field's data type.
  • custom_object_field_choicesAllowed options of a Choice field, one row each.
  • custom_object_fieldsTyped fields of a custom object (Section 4.6.3).
  • custom_object_recordsRecords of a custom object (Section 4.6.3).
  • custom_object_relationsLinks from a custom object record to records, projects, parties, people or other custom object records (Section 4.6.3), one row per link.
  • custom_object_typesOrg-defined entity types beyond custom fields (Section 4.6.3).
  • custom_object_valuesOne value of one field of one custom object record (Section 4.6.3), in the typed column of the field's data type.
  • dashboard_filtersFilters a dashboard applies to every tile.
  • dashboard_tilesA report placed on a dashboard's 12-column grid.
  • dashboardsA grid of report tiles with shared filters (Section 4.6.4), saved for one member or one team.
  • day_sheetsThe day sheet of a project day: the schedule and notes everyone works from.
  • delegationsTime-boxed delegation of a member's capability to another member of the same org, for example approvals while out of office.
  • deletion_certificatesThe record of an org whose data was deleted (Section 14.7): day 90 of a cancellation or the end of a deletion request's recovery window.
  • deliverable_state_transitionsAppend-only ledger of deliverable state changes, written only by the deliverable transition RPCs and creation.
  • dispatch_assignmentsResponders dispatched to an incident and when each arrived.
  • doc_snapshotsOne live co-edited document per row and field (Section 5, Section 7.3): the merged Yjs state, the update sequence it covers and a plain text projection.
  • doc_updatesYjs updates to a co-edited document since its snapshot, numbered per document, kept for recovery: a reconnecting editor reads what it missed.
  • dock_slotsBooked windows at a loading dock zone.
  • document_versionsAppend-only versions of a document, numbered by the database.
  • documentsDocuments of the org or of a project; project documents follow invariant 2.
  • domain_event_catalogThe webhook event catalog: event codes, subjects and descriptions.
  • domain_eventsAppend-only domain event table that webhook delivery reads (Section 10.1).
  • dsar_request_clockThe 30-day clock of every data subject request (Section 14.3): due 30 days after receipt, or 90 when extended, and whether an open request is overdue.
  • dsar_requestsData subject requests (Section 14.3) with the 30-day clock from receipt.
  • dsar_state_transitionsAppend-only ledger of dsar state changes, written only by the dsar transition RPCs and creation.
  • earned_media_itemsEarned media coverage of a project (gate 8, G8.MEASUREMENT_REPORTED): one row per piece of coverage, sourced and dated, with its link, reach and tone.
  • earning_codesEarning codes payroll lines are paid under, mapped by the payroll integration.
  • email_digest_queueEmail deliveries waiting for a member's next digest.
  • email_templatesEmail templates in packages/email.
  • emergency_codesThe org's emergency codes: its editable copy of the Standard Library codes (xpms.emergency_code, decision D15), listed in sort_order, then code.
  • employment_statusesEmployment statuses an employee engagement records.
  • engagement_boardEngagements as the Engagements and Onboarding pages read them: party name, onboarding progress, documents awaiting a signature or countersignature, deliverables to review and whether each side has rated (Section 4.4.4 stages 6 to 9).
  • engagement_cuesCues of a running order that are an artist's set times (Section 4.4.4: the artist sees set times).
  • engagement_deliverablesWhat an engaged party owes on an engagement (Section 4.4.4 Contractor: deliverables or milestones): a record of the same project, handed in with a document and accepted or returned by the org.
  • engagement_document_state_transitionsAppend-only ledger of engagement document state changes, written only by the engagement document transition RPCs and creation.
  • engagement_document_tokensSigning links for engagement documents (Section 4.4.6): a person without an account opens the document with the link and its access code and signs it.
  • engagement_documentsDocuments exchanged on an engagement: offers, agreements, statements of work, riders, settlements (Section 4.4.4), each moving through the Engagement-Document lifecycle.
  • engagement_insured_checksFor each engagement of a vendor and each additional insured the org requires on its project (org-wide or project), the current certificate that names the party with the endorsement.
  • engagement_messagesAppend-only messages on an engagement thread, authored by the session person.
  • engagement_resolvedEngagements as every internal surface reads them (engagement contract engagement_resolved): job title, classification and payment channel joined from canon, and the rate in force read from the agreed rate, then the org's rate card line effective on the start date, then the canon rate card.
  • engagement_state_transitionsAppend-only ledger of engagement state changes, written only by the engagement transition RPCs and creation.
  • engagement_threadsConversation threads between the org and the engaged party on one engagement (Section 7.3 messaging).
  • engagementsA person or an external organization working one project of an org in one external role (Section 4.4.4, engagement contract, decision D16).
  • entitlement_deliveriesEach delivery of a sponsor entitlement (gate 8 sponsor obligations), with the quantity delivered and who recorded it.
  • enumerationsThe org's enumeration values, by domain and sort_order: its editable copy of the Standard Library enumerations (xpms.std_enumeration), or its own.
  • event_check_insAppend-only attendance of workforce events, one per attendee.
  • event_rsvpsRSVPs to workforce events, one per invitee, changed through app.rsvp_to_event.
  • expense_budget_linesThe budget lines a person may post an expense to (finance.expense.write on the project, 1622), as the expense line picker shows them: no quantities, prices or totals, so a field crew member who files expenses never reads the budget (finance.budget.read).
  • expense_receiptsThe receipt photo of an expense, filed from Compass with the expense (Section 4.3 item 11).
  • expense_state_transitionsAppend-only ledger of expense state changes, written only by the expense transition RPCs and creation.
  • expensesExpenses.
  • export_job_columnsColumns an export contains, which set its classification.
  • export_jobsRequested exports (Section 4.6.4) with data loss prevention (Section 8.6): the highest classification among the exported columns decides who may export and whether the file is watermarked.
  • favoritesPages and records a person pinned in an org's sidebar.
  • feature_flag_overridesPer-org flag overrides set by platform staff, for progressive rollout and support.
  • feature_flagsFeature flags and their defaults.
  • feed_acknowledgmentsAppend-only record of members acknowledging a feed post that requires it, one per member.
  • feed_postsA feed post (Section 4.9 Feed): an announcement, update, quick poll or recognition for an audience, with pinning, required acknowledgment, per-post reaction and comment switches and a publish time.
  • feed_reactionsReactions on feed posts, from the curated reaction set.
  • feedback_submissionsFeedback a person sent the platform team from the widget in Atlas or Gateway (Section 11.7, A65-022): their message, the page context the widget showed them before sending and an optional screenshot they chose.
  • file_access_logEvery view, download, export and share of a stored file (Section 8.4 access transparency, Section 8.6 data loss prevention).
  • flsa_statusesFLSA statuses an employee engagement records.
  • form_submission_state_transitionsAppend-only ledger of form submission state changes, written only by the form submission transition RPCs and creation.
  • form_submissionsA submitted form: its answers against one template version, score, GPS stamp, signature and approval.
  • form_template_state_transitionsAppend-only ledger of form template state changes, written only by the form template transition RPCs and creation.
  • form_template_versionsAppend-only snapshots of a form template at each publish; submissions answer one version.
  • form_templatesA no-code form (Section 4.9 Forms) with conditional fields, photos, GPS stamp, signature, scoring and approval routing.
  • fulfillment_linesLines of a fulfillment, such as a room night for a guest.
  • fulfillment_state_transitionsAppend-only ledger of fulfillment state changes, written only by app.transition_fulfillment and fulfillment creation.
  • fulfillmentsLodging, catering, travel and amenity fulfillments of a project.
  • fx_ratesExchange rates an org converts with: one unit of base_currency buys rate units of quote_currency on effective_on.
  • gate_criteria_statusGate readiness per project and criterion, derived from the evidence spine.
  • gate_evidenceGate evidence on one evidence spine (Section 3.4, Section 7.4): one row per piece of evidence against a gate criterion.
  • gate_queueVehicles waiting at the site gate and when each was released.
  • geofence_shapesGeofence outlines as GeoJSON for maps and on-device checks (Section 13).
  • geofencesGeofences of a venue as WGS 84 polygons (postgis), used to check that punches and scans happen on site.
  • goods_receiptsGoods received against an approved or sent purchase order.
  • group_membersMembers of a group space.
  • groupsA group space (Section 4.9 Groups): a department, project, crew or custom audience with its own chat and files.
  • guest_check_insAppend-only door check-ins of guest list entries (Section 4.9), with plus-ones admitted and the credential scanned.
  • guest_list_entriesGuest list of a project: each guest with plus-ones and the party whose list it is.
  • handbook_acknowledgmentsAppend-only acknowledgments of mandatory handbook articles, per version, so a new version asks everyone again.
  • handbook_article_versionsAppend-only published versions of handbook articles; the newest is what members read and acknowledge.
  • handbook_articlesA handbook or SOP article (Section 4.9 Handbook and SOPs): searchable, versioned on publish, optionally a mandatory read acknowledged per version.
  • handbook_sectionsChapters of the org handbook, in order.
  • help_desk_team_membersMembers who answer a help desk team's requests.
  • help_desk_teamsInternal teams that answer help desk requests (Section 4.9 Help desk), with their first response target in business hours.
  • idempotency_keysIdempotency-Key ledger per tenant (ADR 0003, Section 5 rule 4): two devices or tabs draining one queue never file a record twice.
  • identity_providersAn org's enterprise identity provider (Section 9): SAML 2.0 or OIDC sign-in through a Supabase Auth SSO provider, optional just-in-time joins with a default role, and optional SCIM 2.0 provisioning authenticated by a hashed bearer token.
  • import_batchesOne commit of an import (Section 4.6.2 step 7): every row it writes records the batch id, and the whole batch can be undone within 7 days of committed_at.
  • import_cell_issuesPer-cell validation issues of an import row (Section 4.6.2 step 4: the reason is shown per cell).
  • import_job_columnsDetected columns of an import and their mapping (Section 4.6.2 steps 2 and 3): the suggestion from the column map, header similarity or the assistant, and the field the person confirmed.
  • import_job_sheetsEvery sheet the worker found in an import's workbook (Section 4.6.2 step 2): its header row, data range and the target the worker proposes, so each sheet can be imported into its own target.
  • import_jobsOne run of the import wizard (Section 4.6.2): the uploaded file, its target, the confirmed column map and its progress.
  • import_mapping_profile_fieldsOne header-to-field pair of a saved mapping profile.
  • import_mapping_profilesSaved column maps that make a repeat import one click (Section 4.6.2).
  • import_row_matchesAn existing row a Valid import row matched exactly on a strong key such as an asset tag or vendor SKU (Section 4.6.2 step 5): committing updates it instead of creating a new row.
  • import_row_resultsOutcome of every source row of an import (Section 4.6.2 steps 4 to 8): its row state and reason, and for a Written row the batch, the row written and what the write did.
  • import_target_fieldsFields columns may map to, per target.
  • import_targetsEntities the import wizard can write.
  • inbound_addressesProject inboxes (Section 4.6.5): mail forwarded to the address lands as an inbound message with its attachments for a coordinator to file.
  • inbound_message_attachmentsAttachments of an inbound message, stored after MIME sniffing, size caps and virus scanning (Section 9).
  • inbound_messagesMail received (Section 4.6.5): forwarded to a project inbox, or a reply to a notification email from a signed reply address.
  • inbox_itemsThe signed-in person's Inbox (Section 11.10 rule 5): live notifications that are not Done or snoozed, sorted into Needs You (approvals, mentions, assignments) and For Your Information, with the approval an approval request is about.
  • inbox_snoozesA notification the recipient snoozed (Section 11.10 rule 5, the H key): it leaves the Inbox until snoozed_until, then returns.
  • incident_mediaPhotos and video attached to an incident.
  • incident_partiesPeople involved in an incident: a known person or a description of an unknown one.
  • incident_state_transitionsAppend-only ledger of incident state changes, written only by the incident transition RPCs and creation.
  • incidentsIncidents of a project (Incident CAD log).
  • inspection_itemsItems of an inspection template.
  • inspection_resultsOne result per template item of an inspection, from the canon Inspection Result enumeration.
  • inspection_templatesReusable inspection checklists.
  • inspectionsInspections performed on a project from a template.
  • insurance_certificate_checksPer certificate: how many parties it names, how many the org requires org-wide, and how many of those it misses.
  • insurance_certificate_insuredsParties a certificate of insurance names, one row per party and endorsement (finding A38-001).
  • insurance_certificatesCertificates of insurance (COIs) a vendor keeps on file.
  • integration_account_mappingsGL accounts of the fixed chart mapped to an accounting connection's accounts.
  • integration_calendar_itemsEvery item a calendar target syncs, in one shape: Meeting and Event records with a start, and shifts.
  • integration_calendar_targetsWhere a calendar connection syncs one kind of item: Meetings, Events or Shifts of the whole org (no project) or one project, into one provider calendar.
  • integration_channel_routesNotification routes of a chat connection: each domain event type of the org or one project posts to one channel.
  • integration_connection_state_transitionsAppend-only ledger of integration connection state changes, written only by the integration connection transition RPCs and creation.
  • integration_connectionsAn org's connection to one provider account (Section 17).
  • integration_external_idsThe external identifier map (Section 17): one row links a local row to its identifier in one connection.
  • integration_file_linksProvider files attached to XOS documents (Section 17 storage: document links and import).
  • integration_inbound_eventsWebhooks a provider sent to XOS (Section 17), recorded once per provider event after the signature checked out, then processed by the integration worker with retries and exponential backoff.
  • integration_ledger_queueUniversal Posting Lines (Section 3.11) of posted journal entries that a Connected accounting connection has not exported yet.
  • integration_payment_queueApproved payments a Connected accounting connection has not received yet, with the counterparty's provider contact when it is mapped.
  • integration_providersThe Section 17 connector catalog in numeric order, so the settings page lists only connectors the database accepts.
  • integration_route_eventsDomain events matched to the channel routes of Connected chat connections.
  • integration_sync_errorsAppend-only per-item errors of sync runs, written by the connector runner, so an admin sees which rows failed and why.
  • integration_sync_run_state_transitionsAppend-only ledger of integration sync run state changes, written only by the integration sync run transition RPCs and creation.
  • integration_sync_runsSync runs of a connection (Section 17): what moved, how many attempts it took and why it failed.
  • interviewsInterviews and auditions of an applicant (Section 4.4.4 selection).
  • invite_linksShareable invitation links (Section 4.8.1): anyone signed in with the link joins with its role until it expires, runs out of uses or is revoked.
  • invitesInvitation of an email address to an org with a role and expiry (Section 4.8.1).
  • invoice_linesLines of an invoice.
  • invoice_match_resultsThree-way match results, derived from rows the caller may read: variance between the invoice total (subtotal plus tax) and the value received at order prices, whether vendor, currency and amount agree, and whether a mismatch was accepted.
  • invoice_matchesThree-way matches of a payable invoice to a purchase order and a goods receipt (invariant 17).
  • invoice_state_transitionsAppend-only ledger of invoice state changes, written only by the invoice transition RPCs and creation.
  • invoice_totalsInvoice totals and settlement, NULL-aware: subtotal and tax are NULL while any line is unpriced.
  • invoicesInvoices issued to clients (Receivable) and received from vendors (Payable).
  • job_queueBackground jobs (Section 7.3).
  • join_requestsRequests to join an org (Section 4.8.1), approved by a member holding org.members.manage.
  • journal_entriesJournal entries.
  • journal_linesLines of a journal entry: one account, dimension 1 and 2, and either a debit or a credit.
  • journal_state_transitionsAppend-only ledger of journal entry state changes.
  • kiosk_devicesShared clock-in kiosks.
  • kiosk_pinsKiosk PINs of org members, stored only as bcrypt hashes and set through app.set_kiosk_pin (invariant 8).
  • labor_agreementsCollective bargaining agreements an org works under (engagement contract labor_agreement).
  • legal_acceptancesAppend-only log of legal document acceptances (Section 14.4): who accepted which version of which document, when and from which IP, and for which org when accepted on its behalf.
  • legal_holdsLegal holds (Section 14.3): while a hold is active, the purge job keeps the org's rows in the held table, or in every table when no table is named, past their retention.
  • lifecycle_transition_rulesAllowed transitions of every lifecycle, so interfaces offer only moves the database accepts.
  • listing_reportsReports of a listing by anyone who can see it (Section 4.4.3 abuse).
  • lost_found_claimsClaim records of lost items: who claimed it, how to reach them, their proof, and whether the item was returned.
  • lost_found_itemsThe lost and found log (Section 4.9): items found on site, with photos as attachments, where they are stored and their claim state.
  • lost_item_state_transitionsAppend-only ledger of lost item state changes, written only by the lost item transition RPCs and creation.
  • marshalling_logAppend-only marshalling yard log: staging, moves and releases as they happen.
  • measurement_metric_tagsThe Bible sustainability tags each sustainability figure is reported against (Section 4.10).
  • measurement_metricsFigures a project measures against its gate 1 objectives (Section 4.10): sustainability, audience, earned media and sentiment, with the canon benchmark where canon states one.
  • measurement_unitsUnits a project figure or objective is entered in, with the exact factor to the base unit of their dimension and the unit reports show each dimension in for metric and imperial readers.
  • medical_encountersMedical encounters at an incident.
  • medical_encounters_maskedMedical encounters with the Restricted, encrypted treatment notes decrypted only for holders of data.restricted.read.medical; masked (NULL, is_masked true) for everyone else.
  • membership_rolesRoles held through a membership; a member may hold several and capabilities are their union (Section 4.8.1).
  • membershipsA person in an organization as an internal member (Section 4.8.1).
  • merge_reviewsFuzzy matches waiting for a person (Section 4.6.2 step 5): an import row whose name plus address is at least 0.85 similar (pg_trgm) to an existing row.
  • moderation_actionsAppend-only moderation decisions on a listing with the statement of reasons sent to the affected party (EU Digital Services Act article 17).
  • moderation_appealsAn appeal of a moderation decision (A90; Digital Services Act article 20; Acceptable Use Policy): by the affected party against a removal or restriction, or by the reporter against no action on their report, within six months.
  • notification_categoriesNotification categories for the preference matrix.
  • notification_deliveriesOne notification on one outside channel (Email, SMS, Push), partitioned on the notification's month so both expire together.
  • notification_preferencesThe preference matrix: one row per member, category and channel the member set.
  • notification_settingsQuiet hours and digest choice of a member (Section 14.5: quiet hours by recipient time zone).
  • notification_templatesCategory and email template of every notification kind and channel.
  • notificationsInbox notifications (Section 7.3), one per recipient, in monthly partitions.
  • oauth_appsOAuth 2.1 clients an org registers for user-delegated access to the public API (Section 10.1).
  • oauth_grantsConsent a person gave an OAuth app: the capability groups it may use on their behalf.
  • occupancy_countersA live occupancy counter (Section 4.9) for a space or entrance on a project: the current count against the permitted occupant load, with alerts at 80, 90 and 100 percent.
  • occupancy_countsAppend-only door counts: people in (positive) and out (negative), with the count after each.
  • offboarding_open_recordsOpen records a departed person still owns, is accountable for or is assigned to, for the offboarding checklist.
  • offboardingsThe offboarding checklist opened when a membership ends (Section 4.8.1): the org reassigns the person's open records, then completes it.
  • offer_state_transitionsAppend-only ledger of offer state changes, written only by the offer transition RPCs and creation.
  • offer_versionsAppend-only terms of an offer, one row per proposal or counter, numbered by the database.
  • offersOffers on applications (Section 4.4.4 stage 5).
  • onboarding_item_statusOnboarding progress per item, derived: the latest verification, whether the item passes or carries over from the same party's earlier engagement with the org, and whether an expiry reminder is due.
  • onboarding_itemsOne onboarding requirement for one engagement: what the party submitted.
  • onboarding_requirementsAn org's onboarding packet requirements (Section 4.4.4), per role type and jurisdiction.
  • onboarding_verificationsAppend-only verifications of an onboarding item.
  • opportunitiesOpportunities published to external parties (Section 4.4.3): staffing calls, RFQs and RFPs, talent bookings, contractor scopes and sponsorship packages.
  • opportunity_alertsMatches of a saved search to a published opportunity, written by the platform matcher; delivery is A18's notification service.
  • opportunity_invitationsNamed people and external accounts invited to an opportunity; for Invited visibility they are the only ones who see it.
  • opportunity_position_countsNumber of positions of each opportunity, derived from its positions.
  • opportunity_positionsPositions an opportunity fills, one row each, with call times.
  • opportunity_questionsApplication questions of an opportunity.
  • opportunity_requirementsRequirements of an opportunity (Section 4.4.3): certifications, insurance minimums and equipment.
  • opportunity_state_transitionsAppend-only ledger of opportunity state changes, written only by the opportunity transition RPCs and creation.
  • org_brandsAn org's white-label brand (Section 12), applied on Atlas, Gateway, emails, PDFs and Compass.
  • org_cancellationsAn org's cancellation (Section 14.7): read-only for 30 days with the full export available, data deleted at day 90 with a deletion certificate to the Owner.
  • org_deletion_requestsAn Owner's request to delete the org (Section 14.7), separate from cancellation: made with step-up and the typed org name, it ends the subscription and makes the org read-only at once; the Owner may recover the org for 7 days, after which its data is deleted and the Owner receives a deletion certificate.
  • org_departments_in_useA canon department the org works in (Section 4.5.6 item 8).
  • org_disciplines_in_useA canon discipline the org works in (Section 4.5.6 item 8), always under a department it also works in.
  • org_domainsDomains an org claims (Section 12, Section 4.8.1, Section 4.8.3): custom Atlas and Gateway hosts, email sending domains, and verified domains that earn the verified badge and may allow automatic join with a default role.
  • org_exportsEvery full export of an org (Section 14.7, Section 14.8): the archive of JSON and CSV for each table, the org's stored files and a manifest, built with the Owner's own row level security.
  • org_ip_allowlistNetworks allowed to reach Atlas and the API for an org (Section 9, Section 4.5.6 item 10).
  • org_legal_entitiesLegal entities an org trades as, with their tax identifier, fiscal year start and base currency (Section 4.5.6 item 3, Section 7.3).
  • org_legal_entities_maskedLive org legal entities with the Restricted tax identifier decrypted for holders of data.restricted.read.tax and masked (NULL with is_masked true) for everyone else (Section 8.3).
  • org_location_defaultsWhat a new venue of the org starts with (Section 4.5.6 item 9): its jurisdiction and its IANA time zone.
  • org_mandatory_notification_categoriesNotification categories an org makes mandatory (Section 4.5.6 item 29), for example safety: every channel the org default has on stays on for every member.
  • org_module_statesWhether a module is on for an org (Section 4.5.2, Section 4.5.6 item 13).
  • org_notification_defaultsThe org's notification default per category and channel (Section 4.5.6 item 29): what a member receives until they choose.
  • org_state_labelsAn org's display labels for the nine canon record states (Section 4.10).
  • organization_case_studiesCase studies on an organization's profile (Section 4.8.2).
  • organization_profile_capabilitiesWhat an organization offers, each a canon category URID (Section 4.8.2).
  • organization_profile_membersTeam members who opted in to appear on their organization's profile (Section 4.8.2).
  • organization_profilesAn organization's profile (Section 4.8.2), shown in Gateway at /c/{handle}: tenant orgs and external accounts alike, so a vendor that later subscribes keeps it.
  • organization_service_regionsRegions an organization serves, as canon jurisdictions (Section 4.8.2).
  • organization_verification_requestsAn org's request to verify its business identity (Section 4.8.3): a Stripe Identity verification session or a business registry entry, checked by the verifier job, which records a passed check through A30's app.record_organization_verification.
  • organization_verificationsBusiness identity verifications of an organization (Section 4.8.3), recorded only by the platform after Stripe Identity or a business registry check.
  • organizationsEvery company on the platform: a tenant (with a subscription), an external account, or both (Section 4.8.1).
  • osha_annual_summariesThe Form 300A of an establishment and year: employment information and the company executive's certification.
  • osha_casesRecordable work-related injuries and illnesses (29 CFR Part 1904): each row is a Form 300 log entry and its Form 301 incident report.
  • osha_establishmentsEstablishments whose OSHA injury and illness records an org keeps (29 CFR 1904.30): the Form 300 header and the Form 300A establishment information.
  • ownership_transfersAn Owner's offer to hand the org to another member (Section 14.7).
  • partner_agreementsWholesale terms of a partner org (Section 4.6.1): the platform bills the partner at list price less the discount.
  • partner_client_pricesWhat a partner charges a client org each month (Section 4.6.1; ADR 0033 decision 66).
  • partner_default_brandsThe brand a partner's client orgs inherit (Section 4.6.1, Section 12).
  • partner_standing_grantsA standing grant written into the partner and client agreement (Section 4.6.1): the client Owner lets the partner's staff read one area of the client org until an expiry of at most a year, citing the agreement clause.
  • party_messagesAppend-only messages on an org-level party thread, authored by the session person.
  • party_threadsOrg-level conversations between an org and an external person or account, beyond any one engagement (Section 11.10 habit 8).
  • passed_opportunitiesListings a Gateway user passed on (Section 11.12 Discover: swipe left to pass, with a Pass button for both).
  • pay_period_state_transitionsAppend-only ledger of pay period state changes, written only by the pay period transition RPCs and creation.
  • pay_periodsPay periods of an org.
  • pay_ratesAppend-only pay rate ledger: a person's rate in a role from a date.
  • pay_rates_maskedPay rate ledger with the Restricted rate masked unless the caller holds data.restricted.read.payroll or the rate is their own.
  • pay_transparency_rulesPay transparency rules by jurisdiction: where an opportunity cannot be published without a pay range.
  • payment_applicationsHow much of a payment settles which invoice.
  • payment_state_transitionsAppend-only ledger of payment state changes, written only by the payment transition RPCs and creation.
  • paymentsPayments made to or received from a counterparty.
  • payout_accountsWhere an org pays a payee: a reference held by the payment provider, never bank details (Section 4.4.4).
  • payroll_exportsAppend-only record of each export of an approved payroll run to a provider.
  • payroll_line_amountsPayroll lines with derived amounts; rate and amount are masked unless the caller holds data.restricted.read.payroll.
  • payroll_linesLines of a payroll run: hours paid under an earning code at the rate the run calculated.
  • payroll_run_state_transitionsAppend-only ledger of payroll run state changes, written only by the payroll run transition RPCs and creation.
  • payroll_runsPayroll runs of a pay period.
  • peopleOne human, linked to at most one sign-in (Section 4.8.1).
  • per_diemsPer diem allowances paid to a person for a day on a project, at most one per person, project and day.
  • permit_requirementsPermits a project needs, generated by app.generate_permit_requirements from the canon permit rules of the project's jurisdiction chain (Bible tab 15).
  • person_calendar_feedsA person's own iCalendar feed across every org they work with through an engagement (Section 4.5.8 Work, Upcoming; Section 4.6.5): their published shifts and the meetings, milestones and deadlines shared with them, read through the api_external projections.
  • person_certificationsCertifications on a person's profile, kept by the person across orgs (Section 4.8.2, ADR 0019 carry-over).
  • person_emergency_contactsPeople to call when something happens to the person on site (Section 4.5.6 item 10, Section 4.3 item 13), in the owner's order, at most five live.
  • person_languagesLanguages a person speaks and how well.
  • person_linksLinks a person shows on their profile, such as a website or social profile.
  • person_loyalty_programsTravel loyalty programs a person belongs to (Section 4.5.6 item 10, travel profile), at most twenty live.
  • person_notification_preferencesAn external party's own notification choice per category and outside channel (Email or Push), set in Gateway settings.
  • person_notification_settingsA person's own quiet hours, for notifications from orgs they have no membership in (external parties and marketplace alerts, A89).
  • person_profilesA person's profile (Section 4.8.2), owned by the person and shown in Gateway, linked from Atlas and compact in Compass.
  • person_push_devicesA person's own devices for push (A101, decision 69): a Compass device's Expo push token or a Gateway browser's Web Push endpoint.
  • person_referencesReferences a person lists.
  • person_skillsSkills a person lists, each a canon category URID (Section 4.8.2), in the owner's order.
  • person_work_detailsA person's work details (Section 4.5.6 item 10): uniform sizes, dietary and accessibility needs and the travel profile.
  • personal_access_token_scopesA capability group a personal API token may use (Section 4.5.6 personal settings item 15), one row per group.
  • personal_access_tokensPersonal API tokens (Section 4.5.6 personal settings item 15): one person's token for one org, where the org allows them (developer.personal_tokens).
  • personal_setting_valuesA person's own setting values (Section 4.5.6 Personal settings), shared by Atlas, Gateway and Compass.
  • plan_overridesAn operator's time-boxed change to an org's plan (A90, Section 16): the whole plan, one plan feature on or off, or one countable limit.
  • plansSubscription plans of Section 16.
  • platform_operator_actionsAppend-only ledger of operator console actions (A90): who on the platform team did what, to which tenant and row, and why.
  • platform_operatorsThe platform team (A90, Section 4.1 Platform Operator): one live row per person who may sign in to the operator console, with the role that sets what they may do there.
  • po_acknowledgmentsA vendor's acknowledgment of a purchase order the org sent (Section 4.4.4 Vendor: PO acknowledgment), once per order, append-only.
  • po_change_order_state_transitionsAppend-only ledger of po change order state changes, written only by the po change order transition RPCs and creation.
  • po_change_ordersChanges to an approved purchase order.
  • po_linesLines of a purchase order.
  • poll_optionsOptions of a feed poll, 2 to 10, in order.
  • poll_votesAppend-only votes in a feed poll.
  • pollsA quick poll in the feed, attached to a post of kind Poll.
  • pool_membersPeople and external accounts in a pool with their standing (Section 4.4.3).
  • portfolio_itemsPortfolio and EPK items (Section 4.8.2): media the person uploaded or links to their work.
  • posting_linesThe Universal Posting Line (Section 3.11, Bible tab 36): every posted journal line in the one export shape projected to Xero, QuickBooks Online, NetSuite and Ramp.
  • prequalificationsVendor prequalifications.
  • price_booksNamed price books an org sells from, each in one currency (Section 7.3).
  • privacy_signalsOpt-out signals received (Section 14.3): a Global Privacy Control header or an explicit Do Not Sell or Share request.
  • product_eventsConsent-gated, first-party product analytics events (Section 11.14, A65-022): what happened in which app, on which route template or workflow step, keyed to a random browser session.
  • product_funnel_hourlyProduct analytics in hourly buckets (instants, not calendar days): events and distinct browser sessions per app, event, workflow step and route template, the funnel the platform team checks against the Sections 11.11 to 11.13 targets.
  • production_state_transitionsAppend-only ledger of production state changes, written only by app.transition_production and project creation.
  • profile_section_visibilityVisibility the owner set for one section of their profile (Section 4.8.3).
  • profile_share_fieldsThe fields of a profile share, one row per field the owner chose to share, with the value at the time of sharing.
  • profile_sharesConsent to share profile fields with one org (Section 4.4.1): the snapshot taken when a person or company applies or is engaged.
  • project_attendance_totalsAttendance totals per project and show for the gate 8 measurement.
  • project_authorityResponding authorities for a project from its venue's jurisdiction (engagement contract project_authority; decision D15).
  • project_billingBilled-to-date and paid-to-date per project and currency, from receivable invoices and their applications.
  • project_capabilitiesCapabilities: capability statements with direction Provide.
  • project_measurement_correctionsAppend-only ledger of every correction, withdrawal and restore of a recorded figure, with the figure before and after and the reason.
  • project_measurement_summaryGate 8 measurement against the gate 1 objectives (Section 4.10), per project and metric, in the metric's base unit: the objective, the figures measured and the outcome.
  • project_measurementsFigures measured on a project (Section 4.10): waste, energy, water and transport, audience and sentiment, each per metric, day and source.
  • project_member_rolesEvery project role a project assignment holds (Section 4.8.1: project roles, many).
  • project_membersOrg members assigned to a project with a project role (Section 8).
  • project_objectivesMeasurable objectives of a project, recorded at gate 1 (canon criterion G1.OBJECTIVES_STATED): one target per metric, which gate 8 measures against (G8.MEASUREMENT_REPORTED).
  • project_phase_transitionsAppend-only ledger of gates passed, written only by app.pass_gate (invariant 9).
  • project_requirementsRequirements: capability statements with direction Require.
  • project_share_scope_nodesScope nodes a project share opens, with their descendants (Section 8.5).
  • project_sharesA project shared with a partner org (Section 8.5).
  • project_state_transitionsAppend-only ledger of project state changes, written only by app.transition_project and project creation.
  • projectsOne engagement with jurisdiction, phase and gates (Section 4.5.1, Section 7.4 Scope).
  • punch_itemsPunch list items: one Task record of subtype Execute each, with where the item came from and where it is.
  • purchase_order_state_transitionsAppend-only ledger of purchase order state changes, written only by the purchase order transition RPCs and creation.
  • purchase_order_totalsPurchase order totals, NULL-aware, with approved change order deltas beside them.
  • purchase_ordersPurchase orders of a project.
  • push_subscriptionsDevices registered for push, per membership, so leaving an org stops its pushes (invariant 3): Compass devices through Expo Notifications (an Expo push token), and browsers through Web Push with VAPID (an endpoint and its keys, 1533).
  • push_ticketsOne push of one delivery to one device through the Expo push service (A65-012, ADR 0030): the ticket Expo returned, or why it refused the message, then the receipt.
  • radio_channel_planThe org's standard radio plan, by zone and channel number: its editable copy of the Standard Library radio channels, or its own.
  • radio_channelsThe radio plan of a project, listed in channel number order.
  • rate_card_linesRates on a rate card.
  • rate_card_lines_maskedRate card lines with the Restricted rate masked (NULL, is_masked true) unless the caller holds data.restricted.read.payroll.
  • rate_cardsAn org's labor rate cards over time (Section 7.4).
  • rating_repliesThe rated side's one public reply to a released rating (Section 4.4.3).
  • ratingsTwo-sided ratings of a completed engagement (Section 4.4.3): the org rates the party and the party rates the org.
  • receipt_linesQuantities received per purchase order line.
  • recent_viewsWhat a person opened (Section 11.7: the last 50 records each person viewed appear before they type): each record, incident, document, SOP or handbook article once, with when they last opened it.
  • recognitionsAppend-only shout-outs (Section 4.9 Recognition) from one member to another, tied to a project or shift and posted to the feed.
  • reconciliation_gapsGaps of each reconciliation: every Gap, and every Unknown against a critical requirement (Section 3.7), which G3.NO_CRITICAL_GAPS reads.
  • reconciliation_linesOne requirement's result in a reconciliation: Met (names the capability), Gap or Unknown.
  • reconciliationsA reconciliation run of a project's requirements against capabilities.
  • record_approvalApproval record attributes.
  • record_assignmentsOrg members assigned to a record, for example crew on a task.
  • record_bookingBooking record attributes: a reservation.
  • record_buildBuild record attributes: the installation act (gate 5).
  • record_checklist_itemsChecklist items of a record, one row per item (Section 7.4), so a tick always lands on the item it names.
  • record_complianceCompliance record attributes: a document that must be on file and current.
  • record_contractContract record attributes: an agreement.
  • record_deadlineDeadline record attributes: an item owed.
  • record_decisionDecision record attributes: a choice to be recorded.
  • record_dependenciesSchedule dependencies between records of one project.
  • record_distributionDistribution record attributes: what is published or sent.
  • record_documentDocument record attributes: the artifact that exists when the record is done.
  • record_eventEvent record attributes.
  • record_external_visibilityWhich external role types or named parties may see a record (Section 7.4 external_visibility), one row each.
  • record_goalGoal record attributes: an outcome with its target and measurement (gate 1 objectives, gate 8 measurement).
  • record_grantsAccess to an org, workspace, team, project or record granted to a person or another organization with scope and expiry, for example a standing partner grant (Section 4.6.1).
  • record_inspectionInspection record attributes: a check that must be passed.
  • record_meetingMeeting record attributes: a conversation.
  • record_milestoneMilestone record attributes: a condition stated as already true.
  • record_paymentPayment record attributes: a planned movement of money.
  • record_permitPermit record attributes: an instrument issued by the authority.
  • record_recruitmentRecruitment record attributes: filling a role.
  • record_recurrencesRecurrence rule of a record that repeats (Section 4.2 Work), one active rule per record.
  • record_rehearsalRehearsal record attributes: a run-through.
  • record_replansAppend-only replan log (Section 3.10): from Scheduled onward every date or state change of a record is logged here; edits while Proposed or Ready overwrite with no entry.
  • record_reportReport record attributes: a publication.
  • record_riskRisk record attributes: an exposure.
  • record_shiftShift record attributes: the planned block of work for a role (crew shifts in app.shifts staff it).
  • record_state_displayThe display label of each of the nine record states in each org the reader belongs to: the org's own label, or the canon name.
  • record_state_transitionsAppend-only ledger of record state changes, written only by app.transition_record and record creation.
  • record_strikeStrike record attributes: the load-out act.
  • record_supplySupply record attributes: the item received.
  • record_taskTask record attributes.
  • record_timelineTimeline record attributes: a window other records roll up into.
  • record_trainingTraining record attributes: a session delivered.
  • record_watchersPeople following a record to be notified of its changes (Section 4.10).
  • recordsOne table for all 26 record kinds (Bible tab 24, Section 3.10).
  • registered_apprenticesWorkers paid as registered apprentices (WH-347 column 2, RA) and their programs (Statement of Compliance, page 2).
  • report_definitionsReport builder definitions (Section 4.6.4): a source, fields with aggregates, filters, grouping and a chart.
  • report_deliveriesOne email of a scheduled report to one recipient (Section 4.6.4): the run made as that member for the slot, and whether the email went out.
  • report_fieldsColumns of a report, in order, each with its aggregate.
  • report_filtersFilters of a report, in the API filter grammar (ADR 0003).
  • report_runsRuns of a report.
  • report_schedule_recipientsMembers a scheduled report goes to.
  • report_schedulesScheduled delivery of a report as PDF, CSV or .xlsx (Section 4.6.4), to org members only.
  • report_sourcesData a report can be built on.
  • representation_scopesScopes of a representation, one row each: Offers, Advance, Settlement, Documents.
  • representationsAn agency or management account acting for an artist (Section 4.4.1, Section 4.8.1 Representation).
  • required_additional_insuredsParties an org requires its vendors' certificates to name (finding A38-001): org-wide when project_id is NULL, otherwise for vendors engaged on that project as well.
  • requisition_amountsDerived figures of each requisition the caller may read: estimated spend, NULL while unpriced and never zero.
  • requisition_state_transitionsAppend-only ledger of requisition state changes, written only by the requisition transition RPCs and creation.
  • requisitionsStaffing requisitions (Section 7.4 People, playbook Staffing Requisition): a request to staff a canon role on a project.
  • retention_policiesRetention period of every app table, for the Data Retention and Deletion Policy page and the data and privacy settings.
  • rfq_invitationsVendors invited to respond to an RFQ.
  • rfq_response_linesQuoted lines of an RFQ response.
  • rfq_responsesA vendor's response to an RFQ, one per invited vendor, accepted only while the RFQ is Issued and readable only once it is Closed (sealed bids).
  • rfq_state_transitionsAppend-only ledger of rfq state changes, written only by the rfq transition RPCs and creation.
  • rfqsRequests for quotation of a project.
  • rider_linesAsks of a rider and whether each was fulfilled.
  • ridersTechnical and hospitality riders received from talent or vendors.
  • role_assignment_state_transitionsAppend-only ledger of role assignment state changes, written only by the role assignment transition RPCs and creation.
  • role_assignmentsPeople assigned to canon workforce roles on a project (Section 7.4 People, playbook Personnel Roster and Roles Library).
  • role_capabilitiesCapabilities a role grants and how far each reaches.
  • role_libraryThe org's job descriptions per canon role: its editable copy of the Roles Library (xpms.role, decision D12).
  • rolesPlatform system roles (org_id null, generated from capabilities.yaml) and org custom roles built from the capability set (Section 8).
  • run_of_showA show day's running order for a scope node.
  • sandbox_orgsA private sandbox org (Section 11.7, A65-022): one per person, filled from the sandbox template, never billed, sending no email or SMS and open to nobody else.
  • saved_opportunitiesOpportunities a Gateway user saved to come back to (Section 4.4.3 discovery).
  • saved_searchesA Gateway user's saved marketplace search (Section 4.4.3 discovery); alerts go out by email and push.
  • saved_view_defaultsThe saved view a person opens by default on a page (Section 11.15): one per person and collection.
  • saved_view_filtersOne filter of a saved view, in the API filter grammar (ADR 0003).
  • saved_view_sharesA saved view shared with one team of its org (Section 11.15).
  • saved_view_sortsOne sort key of a saved view, in priority order.
  • saved_viewsA person's saved view of a collection (Section 7.3, Section 11.15): view type, grouping and search, with filters and sorts in their own tables.
  • scan_intakeScans a device could not resolve on the spot (Section 13): kept with the device time until resolved once through app.resolve_scan_intake as Matched, Created or Dismissed.
  • schedule_actualsWhen a record actually started and finished, one row per record.
  • schedule_baseline_itemsThe planned window of one record in a baseline.
  • schedule_baselinesNamed snapshots of a project's planned dates.
  • scim_group_mappingsIdentity-provider groups mapped to a role, a team or both.
  • scim_identitiesPeople the identity provider provisions through SCIM: their SCIM id, whether they are active, and the group names last sent.
  • scope_nodesThe scope tree of a project (Section 4.5.1): one engagement root, with standing venues and shows beneath it.
  • search_embeddingsSemantic search index (Section 5, A87): one embedding per published document, SOP and handbook article of an org with search.semantic_enabled on, written by the embedding worker with the service role and replaced when the text changes.
  • self_billed_deliverablesAppend-only link from each self-billed invoice line to the accepted milestone it bills, so a milestone is billed once while its invoice stands.
  • self_billed_timesheetsAppend-only link from each self-billed invoice line to the approved timesheet it bills, so a timesheet is billed once while its invoice stands.
  • self_billing_agreementsThe engaged party's consent, per engagement, that the org generates its invoices from approved timesheets (Section 4.4.5 self-billing).
  • separation_of_duties_rulesThe separation of duties rules the database enforces, with the rule codes refusals name.
  • service_accountsNon-human members with their own audit identity (Settings, API keys and service accounts).
  • setting_choicesAllowed values of each Choice setting, in display order.
  • setting_definitionsRegistered settings with their type, scopes, capability, lock and default, so settings pages offer only what the database accepts.
  • setting_valuesSetting values stored for an org, workspace, team or project (Section 4.5.6).
  • settlement_linesLines of a settlement.
  • settlement_state_transitionsAppend-only ledger of settlement state changes, written only by the settlement transition RPCs and creation.
  • settlement_totalsSettlement totals, NULL-aware: the net is NULL while any line is unpriced, with the unpriced count beside it.
  • settlementsSettlements of engagements (Section 4.5.8).
  • share_linksLinks that open one version of a file without an account (Section 8.6): Public files may have a link without an expiry, Internal links need an expiry, Confidential links need an expiry, an access code and the recipient's email, and Restricted files never get one.
  • shared_certificationsProfile certifications people shared with an org, readable by its members holding people.certification.read while the share stands.
  • shared_reportsReport runs shared with one engagement (Section 4.5.8 Client Reports).
  • shift_claimsClaims on open shifts that wait for a decision under the org's claiming rule (scheduling.open_shift_claiming approval or seniority, Section 4.5.6 item 25).
  • shift_state_transitionsAppend-only ledger of shift state changes, written only by the shift transition RPCs and creation.
  • shift_swapsRequests to hand a shift to another member.
  • shiftsCrew shifts: one person (or an open slot) in one role for one block of time on a project.
  • shipment_linesWhat a shipment carries.
  • shipment_trackersA shipment followed through one carrier connection (UPS, FedEx or DHL): the latest normalized status, estimated delivery and delivery time.
  • shipment_tracking_eventsAppend-only carrier scan history of a tracked shipment, normalized.
  • shipmentsShipments to and from a project's sites.
  • shortcut_bindingsKeyboard shortcuts a person rebound in Personal settings (Section 11.7).
  • shortlistsThe org's ranked shortlist of applications for an opportunity, with internal notes (Section 4.4.4 selection).
  • sidebar_item_preferencesA person's own layout of an org's Atlas sidebar (Section 4.5.2): the position and visibility of module groups and items.
  • site_plan_pinsPins on a site plan, positioned as fractions of the drawing's width and height.
  • site_plansSite plans of a project: a drawing that pins are placed on.
  • sms_consent_eventsSMS consent ledger per org and phone number (Section 14.5): opt-ins with their source, STOP opt-outs and HELP requests.
  • sms_consent_statusCurrent SMS consent per org and phone number, derived from the latest Opt In or Opt Out.
  • sms_summary_queueTexts held by quiet hours (ADR 0033 decision 35).
  • sop_acknowledgmentsAppend-only acknowledgments: a person confirms they read a published SOP version.
  • sopsStandard operating procedures.
  • spacesSpaces of a venue, keyed to the URID of the space type.
  • spend_approvalsAppend-only ledger of approvals given under spend authority, written only by approval RPCs.
  • spend_authoritiesSpend authority limits (Section 8.1) by role or person, document type, GL account or cost center scope, and amount.
  • sponsor_asset_state_transitionsAppend-only ledger of sponsor asset state changes, written only by the sponsor asset transition RPCs and creation.
  • sponsor_assetsBrand assets a sponsor entitlement needs (Section 4.4.4 Sponsor: asset approvals): logo, artwork, copy or video, approved or returned by someone other than the uploader.
  • sponsor_entitlementsWhat a sponsor is entitled to on a project and whether it was delivered (gate 8 sponsor obligations).
  • sponsor_proof_of_performanceProof of performance per sponsor entitlement (gate 8): what is owed against what was delivered, NULL-aware.
  • stripe_eventsStripe webhook events, stored once per Stripe event id so a redelivered event is never applied twice (idempotent ingestion).
  • stripe_subscription_linksThe Stripe customer and subscription behind an org's subscription.
  • submittal_state_transitionsAppend-only ledger of submittal state changes, written only by the submittal transition RPCs and creation.
  • submittalsWhat a vendor submits for review on a project (Section 4.4.4 Vendor): shop drawings, product data, samples, method statements and certificates.
  • subscription_state_transition_rulesAllowed subscription state transitions.
  • subscription_state_transitionsAppend-only ledger of subscription state changes, written only by private.transition_subscription and subscription creation.
  • subscriptionsPresent only when an organization uses Atlas (Section 4.8.1).
  • supplier_diversity_certificationsSelf-declared supplier diversity certifications (Section 4.4.1) of a person or an external account, used only where an org runs a supplier diversity program and shared one org at a time under separate consent (app.supplier_diversity_shares).
  • supplier_diversity_eventsThe owner's access log for their supplier diversity certifications (Section 8.4 access transparency): every change they make, every share and revocation, and every read by an org, never a value.
  • supplier_diversity_sharesAn owner sharing one supplier diversity certification with one org that runs a supplier diversity program, under a supplier_diversity consent record for that org (Section 4.4.1: separate consent).
  • support_session_accessesEach read an operator made during a platform support session (A90, Section 8): which session, which operator, which area and when.
  • support_session_grantsThe record grants a support session issued, one per read capability, so ending the session ends each of them.
  • support_sessionsA support session (Section 4.6.1, Section 8): the org's Owner lets its partner's staff (1060) or the platform team (A90) read the org for at most 24 hours.
  • support_ticket_diagnosticsDiagnostics a requester chose to attach to a support ticket (Section 11.16), with the moment they consented.
  • support_ticket_messagesThe conversation on a support ticket, oldest first.
  • support_ticket_state_transitionsAppend-only ledger of support ticket state changes, written only by the support ticket transition RPCs and creation.
  • support_ticketsA request for help (Section 11.16): to the org's own admins (Organization queue) or to the platform team (Platform queue).
  • suppression_listAddresses an org sends nothing to on a channel (Section 14.5 CAN-SPAM, CASL and TCPA): hard bounces and complaints from the provider, unsubscribes, STOP replies and manual entries.
  • survey_answersAppend-only answers of a survey response, one per question.
  • survey_participationsAppend-only record that a member has responded to a survey, so each member responds once.
  • survey_questionsQuestions of a pulse survey, in order.
  • survey_responsesAppend-only survey responses.
  • survey_state_transitionsAppend-only ledger of survey state changes, written only by the survey transition RPCs and creation.
  • surveysA pulse survey (Section 4.9 Polls and surveys) for an audience, anonymous by default, whose results show only once the minimum number of responses is met.
  • swap_state_transitionsAppend-only ledger of swap state changes, written only by the swap transition RPCs and creation.
  • sync_mutationsAppend-only replay ledger of mutations applied for offline devices (Section 13).
  • sync_rpcsRPCs an offline device may replay through app.apply_sync_mutation.
  • system_bannersPlatform-wide in-app banners (A90, Section 4.10): maintenance windows, incidents linked to the status page, plan notices and other notices, scheduled in instants for every shell or one.
  • talent_poolsAn org's talent and vendor pools (Section 4.4.3).
  • tax_formsTax forms a payee gives an org (W-9, W-8BEN, W-8BEN-E; Section 14.9).
  • tax_jurisdictionsTax jurisdictions an org collects or pays tax in, bound to a canon jurisdiction.
  • tax_ratesTax rates of a tax jurisdiction over time.
  • team_membersMembers of a team.
  • teamsWorking groups inside an org, distinct from canon teams (Section 7.3).
  • template_applicationsAppend-only record of each project created from a template, the version used and what it created.
  • template_itemsItems of a template version, in order: scope nodes created under the new project's engagement root, and records created in the new project.
  • template_versionsVersions of a template: project defaults and ordered items.
  • templatesOrg templates (Section 4.10): reusable starting points for projects.
  • thread_readsRead receipts: when each person last read each engagement or party thread.
  • thread_subscriptionsWho follows a thread.
  • time_entriesClock-in and clock-out punches.
  • time_entry_auditAppend-only audit of every change to a time entry: who (created_by), when (created_at) and the diff (an audit diff, a documented JSON exception).
  • time_entry_correctionsRequested corrections to a time entry.
  • time_off_policiesTime off policies of an org.
  • time_off_requestsRequests for time off under a policy.
  • time_off_state_transitionsAppend-only ledger of time off state changes, written only by the time off transition RPCs and creation.
  • timesheet_approvalsApprovals given to a timesheet with the minutes approved at that moment.
  • timesheet_hoursWorked minutes per timesheet, derived from its time entries, and whether an entry is still open.
  • timesheet_state_transitionsAppend-only ledger of timesheet state changes, written only by the timesheet transition RPCs and creation.
  • timesheetsA person's time on a project for a period.
  • tip_dismissalsA contextual tip a person has seen and dismissed (Section 11.16).
  • tour_progressA person's progress through one guided tour (Section 11.16).
  • training_assignmentsCourses assigned to members, with a due date.
  • training_completionsTraining completion records (Section 4.9 Training): every attempt with its quiz score, and for a pass a certificate number and expiry.
  • training_course_state_transitionsAppend-only ledger of training course state changes, written only by the training course transition RPCs and creation.
  • training_coursesA short training course (Section 4.9 Training) of lessons and quizzes, with completion records and expiry, linked to a role, a certification and a gate criterion.
  • training_lesson_progressAppend-only record of reading and video lessons a learner finished.
  • training_lessonsLessons of a training course, in order: readings, videos and quizzes.
  • training_quiz_keysThe correct option of each quiz question.
  • training_quiz_questionsQuestions of a quiz lesson with their options.
  • trash_itemsTrash (Section 4.10): soft-deleted rows of the tables in private.trash_tables, read with the reader's own row level security.
  • travel_segmentsFlights and ground transport for the people a project moves.
  • union_local_ratesRates a union local sets for a role over time.
  • usage_eventsMetered usage (Section 16), one row per counted act, in monthly partitions.
  • usage_rollupsClosed monthly usage totals per org and meter: the billing record reported to Stripe.
  • user_capability_grantsA capability granted to one member beyond their roles, org-wide or for one scope, time-boxed (Section 8).
  • vendor_bank_accountsBank accounts a vendor is paid into.
  • vendor_bank_accounts_maskedVendor bank accounts with the Restricted numbers masked (NULL with is_masked true) unless the caller holds data.restricted.read.banking (Section 8.3).
  • vendor_bank_detail_changesAppend-only log of every person who created or edited a vendor's bank details.
  • vendor_class_assignmentsWhich classes a vendor belongs to; a vendor may hold several.
  • vendor_class_entitlementsWhat a vendor class may use on site, one row per module (Advance, Access, Credentials, Parking and so on): the org's editable copy of the Standard Library vendor entitlements, or its own.
  • vendor_classesVendor classes an org sorts its vendors into, optionally adopted from the Standard Library class.
  • vendor_productsWhat a vendor sells, bound to a catalog item or canon element, with the vendor's SKU and price.
  • vendor_scorecardsVendor performance scores per period, optionally for one project.
  • vendor_state_transitionsAppend-only ledger of vendor state changes, written only by the vendor transition RPCs and creation.
  • vendorsThe vendor facet of a counterparty (Section 7.4: a party with a vendor facet), one per counterparty.
  • venuesVenues the org produces in (Section 7.4 Places, engagement contract).
  • verbiage_termsThe org's controlled vocabulary with casing rules.
  • wage_determinationsPrevailing wage minimums a jurisdiction imposes on a role over time.
  • warehouse_deliveriesEvery warehouse delivery (Section 7.3 warehouse_deliveries): when it ran, what it wrote and how many classified columns it withheld.
  • warehouse_delivery_filesOne file a warehouse delivery wrote: its object key, rows, bytes and SHA-256, and how many columns it delivered and withheld.
  • warehouse_destinationsA customer's own bucket that receives the org's nightly warehouse files (Section 4.6.4, Enterprise).
  • warehouse_providersWarehouse providers and whether XOS can deliver to them yet.
  • weather_alert_rolesThe canon roles the project's emergency plan names for each weather level; the people assigned those roles on the project receive the alerts.
  • weather_alertsWeather alerts raised by readings: one active alert per hazard at the highest level met, cleared when a reading falls below every level.
  • weather_readingsAppend-only weather readings on site, in the hazard's unit (mph, mi, F).
  • weather_thresholdsWeather action thresholds of a project (Section 4.9 Weather monitoring): one value per hazard and level, with the emergency plan source it comes from.
  • webhook_deliveriesOne delivery of one domain event to one endpoint (ADR 0003), in monthly partitions.
  • webhook_endpoint_eventsEvent types an endpoint subscribes to, one row per endpoint and event type.
  • webhook_endpointsOutbound webhook endpoints of an org (Section 10.1, ADR 0003).
  • white_label_graceWhite label kept after a downgrade (Section 12): when an org's plan stops including white label, its brand without "Powered by XOS" and its custom domains stay until the end of the billing period already paid for, with notice to every Owner, then revert to default branding.
  • wholesale_statement_linesOne client org on a wholesale statement: its plan, list price, wholesale amount and the price the partner charges it.
  • wholesale_statementsWhat the platform bills a partner for one month (Section 4.6.1): every client org at its plan's list price less the partner's wholesale discount.
  • work_detail_eventsThe person's own access log for their work details (Section 8.4 access transparency): every change they make, every share and revocation, and every read or reveal by an engaging org, with the categories and changed column names but never a value.
  • work_detail_sharesA person's consent to share chosen categories of their work details with the org that engages them, for one engagement (Section 4.5.6 item 10, Section 14.3).
  • work_order_bidsBids on a work order, one row per bidder submission.
  • work_order_state_transitionsAppend-only ledger of work order state changes, written only by the transition RPCs and work order creation.
  • work_ordersWork orders: scoped work put out for bids, awarded to one bid and carried out (Section 4.2 Work).
  • workforce_eventsA briefing, crew call or meeting (Section 4.9 Events) for an audience, with RSVP, location, agenda and check-in.
  • workspace_membersMembers assigned to a workspace.
  • workspacesA division of an org, for example a city office or a venue group, that scopes projects and members (Section 4.5.1).
  • zonesAccess and operations zones of a venue, used by the access grid and radio plan.

xpms

El canon: la Biblia y el Playbook de XOS como datos publicados, de solo lectura.

  • agency_functionFunctions an agency serves: emergency responders and regulators (decision D15).
  • arrangementThe commercial arrangement: a standing retainer or per-engagement work (decision D16).
  • arrangement_classificationPermitted pairs of arrangement and classification; Retainer is Independent Contractor only.
  • bridge_discipline_teamTeams that deliver a discipline.
  • bridge_element_metricMetrics that apply to an element.
  • bridge_element_permitPermit rules an element triggers.
  • bridge_element_phasePhase participation of an element, multi-valued (Section 3.4).
  • bridge_element_tagSustainability and compliance tags of an element.
  • bridge_touchpoint_disciplineDisciplines a touchpoint is delivered through, from the URIDs of the catalog items that realize it.
  • canon_labelTranslated canon labels, one per vocabulary, canon code and locale (Section 15, ADR 0053).
  • canon_statementNarrative Bible rows that are statements rather than dimension members: the cover, the silence rule, identity doctrine notes and build provenance.
  • canon_vocabularyCanon vocabularies whose labels are translated (Section 15, ADR 0053): where each one's codes and English labels live.
  • classification_documentCountry documents a classification requires (W-4, I-9, W-2, W-9, 1099-NEC).
  • classification_organization_typeWhich organization types may use each worker classification; Volunteer only for Nonprofit and Public Agency (rule XOS-ENG-6).
  • declared_gapDeclared gaps (doctrine 3.4): a gated phase with no Active element carries one, ratified by the owner (owner decision 39, 2026-10-23, finding A65-019).
  • departmentThe ten department classes under the reference model names (class_code, name); rows live in xpms.dim_department.
  • dim_actThe three acts PLAN, BUILD and SHOW (Bible tab 04).
  • dim_assertion_rankAssertion ranks 4 to 0 (Bible tab 22).
  • dim_assertion_wordDomain-native assertion words and their shared rank (Bible tab 22): economics, compliance and capability.
  • dim_budget_template_ruleThe budget template specification (Bible tab 34).
  • dim_categoryCategories (Bible tab 03).
  • dim_category_glDefault cost center of each category (Bible tab 31).
  • dim_change_recordThe 3.0 to 4.0 change record (Bible tab 35).
  • dim_cost_center_templateCost center templates (Bible tab 30), dimension 1: standing operations, corporate overhead and one per event scope.
  • dim_counterparty_typeThe counterparty types (Bible tab 28).
  • dim_departmentThe ten locked department classes (Bible tab 01, Section 3.2), listed in numeric order.
  • dim_disciplineDisciplines (Bible tab 02): canon codes .01 to .49 and adopter extensions .50 to .99 within a department.
  • dim_escalation_indexEscalation indices (Bible tab 13) used to carry bands forward in time.
  • dim_facetFacets carried from canon (Bible tab 20).
  • dim_gate_criterionThe 35 gate criteria (Bible tab 06).
  • dim_gl_accountThe fixed 23-account chart (Bible tab 29 and the GL chart CSV).
  • dim_gl_account_typeGeneral ledger account types and their normal balance (Playbook GL Accounts sheet, NORMAL BALANCE).
  • dim_grainGrain (Bible tab 18): class, unit and lot.
  • dim_identifier_classIdentifier grammar (Bible tab 17): identifier, code and token.
  • dim_identity_axisIdentity doctrine axes (Bible tab 21).
  • dim_localeLocales canon labels can be translated into (Section 15).
  • dim_metricCode-derived and modeled metrics (Bible tab 16).
  • dim_permit_rulePermit rules (Bible tab 15), stamped to their jurisdiction.
  • dim_phaseThe nine gated phases with fixed, append-only ordinals (Bible tab 05, Section 3.4).
  • dim_provenanceProvenance ranks (Bible tab 19, Section 3.8): human 100, operator 80, imported 60, agent 40, provider 20.
  • dim_record_classThe five record classes (Bible tab 24): Work, Artifact, Commitment, Control and Time.
  • dim_record_kindThe 26 record kinds (Bible tab 24), each with a definition of done and a title grammar.
  • dim_record_stateThe nine record states (Bible tab 26).
  • dim_record_subtypeThe 124 kind-scoped record subtypes (Bible tab 25).
  • dim_regionCost regions (Bible tab 12).
  • dim_region_multiplierRatified cost multipliers (Bible tab 12).
  • dim_roleThe 61 workforce roles (Bible tab 27) with function name, job title and staffing ratio.
  • dim_staleness_policyStaleness policy for price bands (Bible tab 14): degrade one step at 12 months, to MODELED at 24, expire at 36.
  • dim_stateThe shared state vocabulary (Bible tab 37): five core states plus small domain extensions.
  • dim_tagSustainability and compliance tags (Bible tab 09).
  • dim_teamCanon teams (Bible tab 08).
  • dim_tierThe six tiers of experience (Bible tab 07, Section 3.5).
  • dim_touchpointThe 90 five-sense touchpoints (Bible tab 10) with Base, Elevated and Premium grades.
  • dim_unit_aliasUnit bases used by canon (the Item Catalog unit_basis values, and hour and week, which owner decision 39 adds with the time dimension).
  • dim_unit_dimensionPhysical dimensions of units (count, length, time and so on).
  • dim_upl_fieldThe Universal Posting Line (Bible tab 36): one export shape and its platform mappings.
  • dim_urn_namespaceURN kinds resolvable under urn:xpms (Section 3.1): urn:xpms:{kind}:{key}.
  • element_gtinsGTINs bound to elements.
  • element_price_bandsPrice bands per element and grade.
  • elementsThe catalog: 1,211 elements (Bible tab 32 and the Item Catalog CSV).
  • emergency_codeEmergency codes, global: no organization, project or jurisdiction (decision D15).
  • emergency_protocolThe protocol for one code in one operational domain.
  • emergency_protocol_stepNumbered protocol steps.
  • field_provenanceProvenance of every populated canon field of an element (Section 3.8).
  • gl_accountThe 23-account chart under the reference model names.
  • gradePrice grades Base, Elevated and Premium (decision D11).
  • intakeStaging for proposed canon additions and changes.
  • jurisdictionJurisdictions (Bible tab 11) in third normal form (decision D19): the country derives from the ID; unit system and currency are stored on the country and inherited; code sets are rows of jurisdiction_code_set; jurisdiction_resolved returns tab 11 exactly.
  • jurisdiction_agencyThe agency serving each function in a jurisdiction, reached through the project's venue (decisions D15 and D19).
  • jurisdiction_code_setCode sets a jurisdiction adopts, one row each (Bible tab 11, primary_code_sets), in their stated order.
  • jurisdiction_resolvedJurisdictions with inherited unit system and currency resolved and code sets listed in order: Bible tab 11 exactly.
  • label_mappingPlaybook labels that are not canon values, each mapped to the closest existing canon or lifecycle value (owner decision 25, 2026-10-19).
  • operational_domainOperational domains an emergency protocol is written for.
  • organization_typeLegal forms of an organization (decision D17).
  • overtime_ruleOvertime and double-time multipliers, stored once as numbers (decision D14).
  • pay_basisHow pay is computed (decision D16).
  • pay_basis_classificationLawful or permitted pairs of pay basis and classification.
  • playbook_columnThe Playbook column map (canon/map/playbook-columns.yaml): every column of every sheet with one disposition.
  • playbook_sheetEvery sheet of the Production Playbook with its destination and manifest facts (canon/source/PLAYBOOK_MANIFEST.json).
  • playbook_sourced_valueCanon values imported from the Production Playbook because the Bible states none (owner decision 25, 2026-10-19).
  • production_templateThe XOS 4.0 Production Template.
  • production_template_metadataCover Page cells: the template's metadata, at their source row and column.
  • production_template_rowsEvery data row of the 27 record-template sheets, keyed by sheet and source row number.
  • production_template_valuesLiteral cell values of template rows.
  • rate_cardLabor Rate Cards (decisions D12 to D14 and D16): only the card's own facts.
  • rate_card_resolvedLabor rate cards with the role title, department, classification label, overtime multipliers and the derived expense account of the role's class.
  • ratificationRatification records.
  • roleThe Roles Library (decision D12): owns role codes and job titles.
  • role_disciplineDisciplines of the Roles Library, each stored once (decision D12).
  • role_rankRanks of the Roles Library, each stored once (decision D12).
  • std_document_libraryXOS Standard Library: Document & Asset Library (Playbook, provenance imported).
  • std_enumerationXOS Standard Library: Enumerations (Playbook, provenance imported).
  • std_radio_channelXOS Standard Library: Radio Channels (Playbook, provenance imported).
  • std_sopXOS Standard Library: SOP Library (Playbook, provenance imported).
  • std_vendor_classXOS Standard Library: Vendor Classes (Playbook, provenance imported).
  • std_vendor_entitlementXOS Standard Library: Vendor Entitlements (Playbook, provenance imported).
  • std_verbiageXOS Standard Library: Verbiage Library (Playbook, provenance imported).
  • supersessionSuperseded codes and their successors.
  • v_category_glEvery category with the expense account of its class (decision D13) and its default cost center (Bible tab 31).
  • v_coordinate_matrixThe 90-coordinate matrix {CLASS}x{PHASE_CODE} (Bible tab 33), computed and never stored, with the number of elements of the class that participate in the phase.
  • v_crosswalk_coverageIdentity crosswalk coverage per category (GTIN to GPC brick to UNSPSC to URID): how many elements carry an UNSPSC and how many have confirmed GTINs.
  • v_element_economicsEvery element at every price grade.
  • v_phase_coverageCatalog coverage per gated phase.
  • v_playbook_access_gridThe Playbook Access Grid sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_activity_logThe Playbook Activity Log sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_advance_requestsThe Playbook Advance Requests sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_asset_assignmentsThe Playbook Asset Assignments sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_asset_inventoryThe Playbook Asset Inventory sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_budget_expensesThe Playbook Budget Expenses sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_categories_urid_masterThe Playbook Categories & URID Master sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_change_ordersThe Playbook Change Orders sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_cost_centersThe Playbook Cost Centers sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_counterparty_typesThe Playbook Counterparty Types sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_cover_pageCover Page cells as stored template metadata, normalized for the round-trip proof.
  • v_playbook_credential_issuanceThe Playbook Credential Issuance sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_crew_shiftsThe Playbook Crew Shifts sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_crew_timesheetsThe Playbook Crew Timesheets sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_departmentsThe Playbook Departments sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_disciplinesThe Playbook Disciplines sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_document_asset_libraryThe Playbook Document & Asset Library sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_emergency_codesThe Playbook Emergency Codes sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_enumerationsThe Playbook Enumerations sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_gl_accountsThe Playbook GL Accounts sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_hospitality_fulfillmentThe Playbook Hospitality Fulfillment sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_incident_cad_logThe Playbook Incident CAD Log sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_inspection_complianceThe Playbook Inspection Compliance sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_labor_rate_cardsThe Playbook Labor Rate Cards sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_locationsThe Playbook Locations sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_marshalling_yard_logThe Playbook Marshalling Yard Log sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_personnel_rosterThe Playbook Personnel Roster sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_po_line_itemsThe Playbook PO Line Items sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_procurement_catalogThe Playbook Procurement Catalog sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_production_scheduleThe Playbook Production Schedule sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_production_tasksThe Playbook Production Tasks sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_projectsThe Playbook Projects sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_purchase_ordersThe Playbook Purchase Orders sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_radio_channelsThe Playbook Radio Channels sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_roles_libraryThe Playbook Roles Library sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_run_of_showThe Playbook Run of Show sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_shipping_manifestThe Playbook Shipping Manifest sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_sop_libraryThe Playbook SOP Library sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_staffing_requisitionThe Playbook Staffing Requisition sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_teamsThe Playbook Teams sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_universal_posting_lineThe Playbook Universal Posting Line sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_vendor_classesThe Playbook Vendor Classes sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_vendor_directoryThe Playbook Vendor Directory sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_vendor_entitlementsThe Playbook Vendor Entitlements sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_verbiage_libraryThe Playbook Verbiage Library sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_playbook_work_ordersThe Playbook Work Orders sheet exported from the database with every cell normalized, for the round-trip proof.
  • v_sheet_access_gridThe Playbook Access Grid sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_activity_logThe Playbook Activity Log sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_advance_requestsThe Playbook Advance Requests sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_asset_assignmentsThe Playbook Asset Assignments sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_asset_inventoryThe Playbook Asset Inventory sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_budget_expensesThe Playbook Budget Expenses sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_categories_urid_masterThe Playbook Categories & URID Master sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_change_ordersThe Playbook Change Orders sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_cost_centersThe Playbook Cost Centers sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_counterparty_typesThe Playbook Counterparty Types sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_credential_issuanceThe Playbook Credential Issuance sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_crew_shiftsThe Playbook Crew Shifts sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_crew_timesheetsThe Playbook Crew Timesheets sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_departmentsThe Playbook Departments sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_disciplinesThe Playbook Disciplines sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_document_asset_libraryThe Playbook Document & Asset Library sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_emergency_codesThe Playbook Emergency Codes sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_enumerationsThe Playbook Enumerations sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_gl_accountsThe Playbook GL Accounts sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_hospitality_fulfillmentThe Playbook Hospitality Fulfillment sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_incident_cad_logThe Playbook Incident CAD Log sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_inspection_complianceThe Playbook Inspection Compliance sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_labor_rate_cardsThe Playbook Labor Rate Cards sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_locationsThe Playbook Locations sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_marshalling_yard_logThe Playbook Marshalling Yard Log sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_personnel_rosterThe Playbook Personnel Roster sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_po_line_itemsThe Playbook PO Line Items sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_procurement_catalogThe Playbook Procurement Catalog sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_production_scheduleThe Playbook Production Schedule sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_production_tasksThe Playbook Production Tasks sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_projectsThe Playbook Projects sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_purchase_ordersThe Playbook Purchase Orders sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_radio_channelsThe Playbook Radio Channels sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_roles_libraryThe Playbook Roles Library sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_run_of_showThe Playbook Run of Show sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_shipping_manifestThe Playbook Shipping Manifest sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_sop_libraryThe Playbook SOP Library sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_staffing_requisitionThe Playbook Staffing Requisition sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_teamsThe Playbook Teams sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_universal_posting_lineThe Playbook Universal Posting Line sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_vendor_classesThe Playbook Vendor Classes sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_vendor_directoryThe Playbook Vendor Directory sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_vendor_entitlementsThe Playbook Vendor Entitlements sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_verbiage_libraryThe Playbook Verbiage Library sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • v_sheet_work_ordersThe Playbook Work Orders sheet as the database holds it: one row per source row, computed columns reproduced in SQL.
  • versionCanon version and generation, with the hashes of the files the seed was generated from.
  • wage_hour_ruleWage-and-hour minimums a jurisdiction adds to its parent; the strictest value up the chain governs (decision D16).
  • worker_classificationThe legal relationship of a worker, independent of pay computation and schedule (decision D16).

api_external

Vistas para partes externas en Gateway y Compass, solo con las columnas que pueden leer.

  • account_membersThe roster of accounts the caller belongs to.
  • advance_packetsSent advance packets the caller answers for (Section 4.4.4).
  • advance_sectionsSections of the caller's advance packets.
  • advance_submissionsAnswers given for the caller's advance recipients, with the review outcome and any reason an answer was returned.
  • applicationsThe caller's applications: their own, their account's, or a represented artist's with the Offers scope.
  • asset_custodyAsset units the caller's engagements hold now: the latest custody row of each unit, while the operational area is open (Section 8.7).
  • availabilityAvailability periods the caller may see; the owner's notes never appear.
  • bid_linesLines of the caller's own bids.
  • bidsThe caller's own sealed bids.
  • change_order_linesLines of change orders shared with the caller, without budget lines.
  • change_ordersChange orders the org shared with the caller for approval.
  • client_approvalsApproval requests to the caller's Client engagements, open and decided, while the operational area is open.
  • clock_punchesThe caller's own clock punches under their engagements while the operational area is open, so Compass shows the clock state offline.
  • credentialsBadges the caller may read (Section 8.7): their own on projects where their engagement is in the operational area, a represented artist's with the Advance scope, and the party badges issued under an artist's engagement for the artist and that representative.
  • cuesCues the caller may read: all cues of a Client's projects, and for artists only their set times.
  • day_sheetsDay sheets of projects where the caller reaches the operational area through an engagement (Section 8.7): the schedule and notes everyone on the day works from.
  • deliverablesWhat the caller's engagements owe (Section 4.4.4 Contractor), with their state, fee, the latest submission and any reason the org returned it, while the operational area is open.
  • deliveriesShipments the caller's account carries to and from a project where its engagement has the operational area open; dock slots for them read from api_external.dock_slots.
  • dock_slotsDock slots of the caller's vendor account: slots booked for shipments it carries and slots booked for its own engagement, while that engagement is in the operational area (Section 8.7).
  • engagement_documentsDocuments of the caller's engagements while the documents area is open.
  • engagement_messagesMessages on the caller's engagement threads.
  • engagement_threadsThreads of the caller's engagements while the engagement area is open.
  • engagementsThe caller's external engagements (Section 8.7): their own, their account's or a represented artist's, while the engagement area is open.
  • goods_receiptsWhat the org received against the caller's purchase orders, for the three-way match.
  • hospitalityTravel, lodging, catering and amenity lines for the caller, or a represented artist with the Advance scope, on projects where that engagement is in the operational area.
  • interviewsInterviews and auditions on the caller's applications: time and place, never internal notes.
  • invoice_linesLines of the caller's invoices.
  • invoicesInvoices between an org and the caller's account, or the caller as an individual (Section 4.4.5): payables the party submitted or was self-billed, in every state, and receivables the org issued to it, once issued.
  • lodgingRoom assignments of the caller, and of a represented artist with the Advance scope, on projects where that engagement is in the operational area (Section 8.7).
  • my_accountsExternal accounts the caller belongs to, with their account roles.
  • my_advance_recipientsAdvance recipients the caller answers for: themselves, their account, or a represented artist with the Advance scope, on sent packets.
  • my_agency_slatesStaff the caller's agency put forward on its applications.
  • my_application_answersAnswers on the caller's applications: their own, their account's, or a represented artist's with the Offers scope.
  • my_availability_calendarsThe caller's availability calendars: their own and those kept for one org.
  • my_certificationsCertifications the caller holds, as each recording org verified them, with whether they are current.
  • my_given_ratingsRatings the caller's side gave orgs after completed engagements, released or still held until the org rates too or 14 days pass.
  • my_opportunity_alertsMatches of the caller's saved searches.
  • my_profile_share_fieldsThe fields of the caller's profile shares, with the value shared.
  • my_profile_sharesProfile shares the caller gave to orgs (Section 4.4.1), their own or their account's, for listing and revoking through app.revoke_profile_share.
  • my_saved_opportunitiesOpportunities the caller saved, newest first by saved_at.
  • my_saved_searchesThe caller's saved marketplace searches and their alert switch (Section 4.4.3).
  • my_token_documentsEngagement documents sent to the caller through signing links they claimed, with whether and when they signed.
  • offer_versionsEvery version of the terms of the caller's offers, highest version in force.
  • offersOffers on the caller's applications: their own, their account's, or a represented artist's with the Offers scope.
  • onboarding_itemsThe caller's onboarding packet items and their progress while the onboarding area is open.
  • opportunitiesOpportunities open to the caller in the marketplace (Section 4.4.3 visibility), and those they have applied to.
  • opportunity_positionsPositions of opportunities open to the caller.
  • opportunity_questionsApplication questions of opportunities open to the caller.
  • opportunity_requirementsRequirements of opportunities open to the caller.
  • party_messagesMessages on the caller's org-level conversations.
  • party_threadsThe caller's org-level conversations, with the latest message time and how many messages from others they have not read.
  • paymentsPayments an org made to the caller's account, for its Account Owners, Admins and Finance members, or to the caller as an individual (Section 4.4.5).
  • payout_accountsThe caller's payout destinations by org: provider and last four only.
  • per_diemsPer diem allowances paid through the caller's engagements (Section 4.5.8 Crew Per Diem), while the operational area is open, as A13's policy reads them.
  • po_linesLines of the caller's purchase orders.
  • projectsProjects the caller reaches through an engagement whose operational area is open (Section 8.7): name and time zone for Compass headers and times.
  • purchase_ordersPurchase orders the org sent the caller's account, for its Owner, Admin and Finance members while the account's engagement on the project has the money area open (Section 8.7).
  • radio_channelsRadio channel plan of the projects the caller works on through an open operational engagement (Section 4.3 Reference), available offline in Compass.
  • ratingsReleased two-sided ratings and their replies, as profiles show them (Section 4.4.3, Section 4.8.2).
  • receipt_linesQuantities received per line of the caller's purchase orders.
  • recordsProject records whose external visibility names the caller's role type, person or organization, on projects where the caller holds an Active or Closing engagement (Section 8.7 operational access).
  • representationsRepresentations the caller is party to, with scopes, expiry and acceptance.
  • rider_linesAsks of the caller's riders and whether each was fulfilled.
  • ridersRiders of the caller's account on projects where it, or an artist it represents, is engaged in the operational area.
  • run_of_showRunning orders the caller may read (Section 8.7): every running order of a project where the caller holds a Client engagement in its operational area, and for artists and their Advance representatives only the running orders that hold their set.
  • self_billing_agreementsSelf-billing consents of the caller's billed engagements, active and revoked.
  • settlement_linesLines of the settlements in api_external.settlements.
  • settlementsSettlements of the caller's engagements once submitted to them (Section 4.5.8 Artist Settlement), while the money area is open.
  • shared_reportsReport runs shared with the caller's engagement (Section 4.5.8 Client Reports) while the share is open: not revoked, not expired and the engagement area reachable.
  • shiftsShifts assigned to the caller's engagements, once published (Section 4.4.4 Crew and Staff: shifts and call times), while the operational area is open.
  • sponsor_assetsBrand assets of the entitlements the caller's sponsor account is owed (journey 47), once the org submits them, while the Sponsor engagement is in the operational area.
  • sponsor_entitlementsEntitlements the caller's sponsor account is owed on a project where its Sponsor engagement is in the operational area (Section 8.7), with due dates and delivery.
  • tax_formsThe caller's own tax forms and their account's; only the last four of the identifier.
  • thread_read_receiptsRead receipts on the caller's engagement and party threads: who on either side last read each thread and when.
  • time_entriesTime worked under the caller's engagements while the operational area is open.
  • timesheetsTimesheets of the caller's engagements with minutes derived from their time entries, while the operational area is open.
  • travelFlights and ground transport booked under the caller's engagements (Section 4.5.8 Crew Travel and Lodging), while the operational area is open.
  • vendor_certificate_insuredsParties named on the certificates each org keeps on file for the caller's account, with the endorsement, while an engagement with that org has the documents area open.
  • vendor_insurance_certificatesCertificates of insurance each org keeps on file for the caller's account, while an engagement with that org has the documents area open.
  • vendor_prequalificationsPrequalifications of the caller's account with each org it is engaged by: scope, decision and validity.