---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Fields on the Authorization Package form

# Fields on the Authorization Package form {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

After you have defined the authorization boundaries for the assets or systems to send through the Authorization to Operate process, you must create an authorization package for that purpose. The package is processed through the seven steps mandated by the RMF.
{#cam-form-authorization-package__table_epy_qrq_f5__entry__2}

| Field | Description |
|-|-|
| Number | Auto-generated authorization package number. |
| Name | A name for the package. |
| Acronym | If needed, an acronym for identifying the package. |
| Missions/Business processes | The appropriate business process for this authorization package. Business processes are defined on the ServiceNow AI Platform; for example, at Policy \& ComplianceScopingBusiness Processes. |
| Active | Activate the authorization package. |
| Step | The RMF step currently assigned to the package. |
| Authorization boundary | The authorization boundary for this package. |
| System purpose | The purpose behind this authorization package. |
[Table 1. Authorization Package form]

{#cam-form-authorization-package__table_epy_qrq_f5}

*[\>]: and then