Permissions and roles reference
This reference describes the access levels and permissions available within DocuBot. Use this guide to understand how roles govern your ability to manage documentation sites, connect repositories, and configure synchronization settings.
User roles
DocuBot uses three primary roles to manage access to the dashboard and the generated documentation.
| Role | Description |
|---|---|
| Owner | The individual who creates the documentation site. Owners have full administrative control over the site configuration, repository sources, and billing settings. |
| Authorized User | A user who has been granted access to the DocuBot dashboard. These users can manage repositories and trigger updates based on the organization’s allowlist requirements. |
| Public Viewer | Any external user who accesses the published documentation URL. Viewers can read all generated content and download PDF exports but cannot access the dashboard or configuration settings. |
Permissions matrix
The following table outlines the specific actions available to each role within the platform.
| Action | Owner | Authorized User | Public Viewer |
|---|---|---|---|
| Create documentation sites | Yes | Yes | No |
| Delete documentation sites | Yes | No | No |
| Connect GitHub repositories via OAuth | Yes | Yes | No |
| Configure sync schedules and frequencies | Yes | Yes | No |
| Trigger manual documentation rebuilds | Yes | Yes | No |
| Modify audience and document type selections | Yes | Yes | No |
| View generated documentation | Yes | Yes | Yes |
| Download PDF exports | Yes | Yes | Yes |
Access and authorization
DocuBot relies on secure, industry-standard authentication methods to verify your identity and protect your repository data.
Account authentication
You must sign in to the DocuBot dashboard using Google Sign-In. Access to the workspace is governed by a domain-based allowlist. If your email domain is not on the authorized list, you will not be able to access the dashboard even after a successful Google sign-in.
Repository access
To generate documentation from private repositories, you must authorize DocuBot via GitHub OAuth. This connection allows DocuBot to securely retrieve your code for the purpose of documentation generation. Public repositories do not require this authorization.
Limitations
Granular team-based permissions or sub-administrator roles are not currently available. All authorized users within a workspace share the same management capabilities for the repositories they track.
Contact support
If you need to adjust your domain allowlist or require assistance with role assignments, please contact our support team:
- Email: support@ademero.com
- Web: https://www.ademero.com
- Phone: 863-937-0272