> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/naviga-subscribe/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/naviga-subscribe/csr-user-guide/csr-introduction/digital-product-management.md). # Digital Product Management You can manage a subscriber's online access from the **digital** tab. From this tab, you can: * edit a subscriber's digital registration * add or remove another user to a subscriber's digital subscription * view a subscriber's digital entitlements ## Navigation To view the **digital** tab, perform a [subscription search](/naviga-subscribe/csr-user-guide/csr-introduction/subscription-search.md), and then select the **digital** tab. ![](/files/-MPGKvaAJ75zh5M_o5es) ## Invite a user to share registration To invite a user to share registration: 1. Select the **invite** button next to any user in the **registrations** grid. A window appears that indicates the amount of remaining registered users. If the user has remaining invites, continue to the next step. Otherwise, you cannot proceed. 2. Add the new users first name, last name, and email address. Select either `owner` or `guest` as the user type. This determines the amount of privilege the user will have. 3. (Optionally, if `owner` is chosen, confirm the disclaimer to the subscriber and check the disclaimer box.) 4. Select the **send invite** button. An email will be sent to the specified email address and the record will appear in the **pending invites** grid. {% hint style="success" %} Use the **add another person to invite** and **remove the last person added** buttons to send multiple invites at once! {% endhint %} To re-invite a user whom has not accepted their invitation: 1. Select the **invite** button next to any user in the **registrations** grid. The **pending invitations** grid will appear. 2. Select the **resend invite** button next to the desired user. An email will be resent to the user. To remove a pending user: 1. Select the **invite** button next to any user in the **registrations** grid. The **pending invitations** grid will appear. 2. Select the **remove** button next to the desired user. The user's invitation will be removed from the **pending invitations** grid and their invitation will become invalid. This request is processed in real-time with the circulation system. ## Edit a user's registration information To edit a user's registration information: 1. Select the **edit** button that corresponds with the user in the **registrations** grid. 2. Toggle whether both the email address and password should be changed. If keeping current, select `keep current` and do nothing. If changing, select `set to...` and add the new password or email. 3. Select the **update** button next to either the new password or email. ## Remove someone from shared registration To remove a user from shared registration: 1. Select the **invite** button next to any user in the **registrations** grid. 2. Navigate to the **current members** grid. 3. Select the **remove** button next to the desired user. ## Registrations grid | Term | Description | | ----------- | ----------------------------------------------------------------------------------- | | Login name | The user's login name, always the user's registered email address. | | State | If registration is verified then \[State] = "Standard" else \[State] = "Unverified" | | Type | Either `owner` or `Guest`. Indicates the amount of access the user has. | | Change date | The date and time the change occurred (`MM-DD-YYYY HH-MM-SS AM/PM`). | Select the **details** button to view the **manage registration** grid. | Term | Description | | -------------- | ----------------------------------------------------------------------------- | | Account number | The subscriber's circulation account number. | | Subscriber | The subscriber's Naviga Subscriber identification number. | | Full name | The subscriber's full name. | | Active | Indicates whether the account is active. | | Type | Indicates the type of access the user has. `Owner` = full, `Guest` = limited. | | Address | The subscriber's billing address. | ## Entitlements grid To view the **entitlements** grid, select the **show entitlements** button. | Term | Description | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Newspaper ID | The newspaper's identification number. | | Newspaper name | The newspaper's name. | | Household level ID | The household subscription level identification number. | | Household level | Means `Household Subscription Level` and refers to a numeric value that is associated with a subscriber’s entitlement access. The numeric values are not fixed and the client determines them. However, `99` typically refers to no access and `1` typically to full access. This field is editable. | | Entitlement ID | The entitlement's identification number. | | Entitlement code | The entitlement's database code. | | Entitlement description | Description of the entitlement, e.g. `eEdition Access`. | You can find more about entitlements here --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.navigaglobal.com/naviga-subscribe/csr-user-guide/csr-introduction/digital-product-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.