The ability for each user to manage a resource depends on the user role assigned to the resource
or parent resource. Permissions are inherited from the parent resource.
User IDs
A user ID uniquely identifies the operator of a CBSD. The SAS uses user IDs to assign a device to
a Customer. Every SAS customer has to provide at least one user ID during Customer account setup.
You can add additional user IDs later.
Devices
The SAS Portal API enables multi-step registration of CBSDs. For devices that need to be
installed by a Certified Professional Installer (CPI), you have two options to initiate the
multi-step registration process:
Option 1: Initiate the process with a CPI account. For this option, the user must be
authenticated with the role_cpi role. First, the user is verified with the
ValidateInstaller()
method, and then they use the
SignDevice()
method to send the CPI-validated configuration to the SAS.
Option 2: Initiate the process with any account. For this option, any user can use the
CreateSigned()
method to create an inactive device configuration that's ready for the CBSD to use. This method
uses device parameters that are encoded with a CPI's private key.
Regardless of which option you use, this process creates an inactive configuration for the device
in the SAS. Then, the CBSD sends a registration request to the SAS. If it’s successful, the device status
changes to "REGISTERED."
For CBSDs that don’t need CPI validation, use the
CreateDevice()
method.
For single-step registration with CPI-encoded data, use the
SAS-CBSD API
defined by WInnForum.
[null,null,["Last updated 2023-12-05 UTC."],[[["\u003cp\u003eThe SAS Portal API enables management of User IDs and Devices within your CBRS network, including creation, viewing, updating, and deletion.\u003c/p\u003e\n"],["\u003cp\u003eUser IDs uniquely identify CBSD operators and are used for device assignment to customers.\u003c/p\u003e\n"],["\u003cp\u003eDevices can be registered through a multi-step process involving CPI validation or a single-step process for devices without CPI requirements.\u003c/p\u003e\n"],["\u003cp\u003eDevice registration can be initiated by a CPI or any user with appropriate permissions, ultimately leading to a "REGISTERED" status upon successful CBSD registration request.\u003c/p\u003e\n"],["\u003cp\u003eUsers' ability to manage resources is determined by their assigned role and inherited permissions.\u003c/p\u003e\n"]]],["The SAS Portal API allows managing User IDs and Devices within a CBRS network. User permissions are role-based and inherit from parent resources. Devices can be registered via a multi-step process involving CPI validation, either initiated with a CPI account using `ValidateInstaller()` and `SignDevice()` methods, or with any account using `CreateSigned()`. Non-CPI validated devices use `CreateDevice()`. After creating an inactive device configuration, a successful CBSD registration request changes its status to \"REGISTERED.\" Single-step registration uses the SAS-CBSD API.\n"],null,["# Resource management\n\nThe SAS Portal API allows you to create, view, update, or delete the following resources within\nyour CBRS network:\n\n- [User IDs](/spectrum-access-system/guides/resource-management#user-ids)\n- [Devices](/spectrum-access-system/guides/resource-management#devices)\n\nThe ability for each user to manage a resource depends on the user role assigned to the resource\nor parent resource. Permissions are inherited from the parent resource.\n\nUser IDs\n--------\n\nA user ID uniquely identifies the operator of a CBSD. The SAS uses user IDs to assign a device to\na Customer. Every SAS customer has to provide at least one user ID during Customer account setup.\nYou can add additional user IDs later.\n\nDevices\n-------\n\nThe SAS Portal API enables multi-step registration of CBSDs. For devices that need to be\ninstalled by a Certified Professional Installer (CPI), you have two options to initiate the\nmulti-step registration process:\n\n- **Option 1:** Initiate the process with a CPI account. For this option, the user must be\n authenticated with the `role_cpi` role. First, the user is verified with the\n [`ValidateInstaller()`](/spectrum-access-system/reference/rest/customers.devices/validate)\n method, and then they use the\n [`SignDevice()`](/spectrum-access-system/reference/rest/customers.devices/signDevice)\n method to send the CPI-validated configuration to the SAS.\n\n | **Note:** The user only needs to validate their CPI identity once.\n- **Option 2:** Initiate the process with any account. For this option, any user can use the [`CreateSigned()`](/spectrum-access-system/reference/rest/customers.devices/createSigned) method to create an inactive device configuration that's ready for the CBSD to use. This method uses device parameters that are encoded with a CPI's private key.\n\nRegardless of which option you use, this process creates an inactive configuration for the device\nin the SAS. Then, the CBSD sends a registration request to the SAS. If it's successful, the device status\nchanges to \"REGISTERED.\"\n\nFor CBSDs that don't need CPI validation, use the\n[`CreateDevice()`](/spectrum-access-system/reference/rest/customers.devices/create)\nmethod.\n\nFor single-step registration with CPI-encoded data, use the\n[SAS-CBSD API](https://winnf.memberclicks.net/assets/CBRS/WINNF-TS-0016.pdf)\ndefined by WInnForum."]]