SharePoint manages document access. Deployment administrators manage HTTPS, the container host, NGINX or IIS URL Rewrite configuration, and Redis.

## Document permissions

Give users the SharePoint permissions needed for their work:

| Access | Expected experience |
|---|---|
| View | Open and read a document. |
| Edit | Open, change, and save a document. |
| No access | The document cannot be opened. |

Check these roles with separate accounts after connecting SharePoint. When a user’s access changes, check that the new permissions apply to document access and saving. See [SharePoint permission checks](../integrations/sharepoint-integration#check-document-access-permissions-and-saving).

## HTTPS connections

Use an HTTPS certificate that matches the BoldDocServer hostname and is trusted by SharePoint and user’s browsers. Restrict access to the certificate’s private key.

NGINX or IIS URL Rewrite provides the public HTTPS endpoint and forwards requests to the BoldDocServer application. Restrict access to the application's internal endpoint to authorized systems. If the HTTPS endpoint connects to the application over HTTPS, ensure that the application certificate is trusted and valid for the hostname used for the connection.

See [Deploy BoldDocServer](../deployment/deploy-bolddocserver) for HTTPS, certificate, NGINX, and IIS URL Rewrite configuration.

## Credentials and access tokens

Keep the license key, Redis password, registry credentials, private keys, and WOPI access tokens private. Access tokens authorize document requests and should be handled as credentials.

- Restrict access to `docker-compose.yaml` after entering your license key and connection string.
- Keep credential files out of source control, or supply values through your deployment platform’s secret store.
- Remove credentials, tokens, and document content from logs and screenshots before sharing them for support.

## Redis and network access

Keep Redis on a private network and allow access only from BoldDocServer and authorized administrators. Use the authentication and encrypted connections provided by your Redis service.

Expose only the public HTTPS endpoint needed by browsers and SharePoint. See [Deployment Prerequisites](../deployment/deployment-prerequisites#network-ports-and-firewall) for the connection list.

## Host maintenance and logs

Restrict administrative access to the container host and Docker runtime. Keep BoldDocServer, the host, and proxy software updated through your organization’s maintenance process.

Limit access to application and proxy logs. Store them according to your organization’s retention policy, and avoid recording tokens, passwords, license keys, or confidential document content.

See [Lifecycle management](../deployment/deploy-bolddocserver#lifecycle-management) for application update commands and [Collect logs for support](../troubleshooting/troubleshooting-reference#collect-logs-for-support) for diagnostic details.