Documents and review
Upload PDF or DOCX files, edit semantic structure, run checks, assign approval, and retain the decision against the exact version reviewed.
See the workflowOrganization portals
Give your organization its own DocAccessible portal.
Reserve a managed subdomain, invite the people responsible for accessibility, use Organization-entitled workflows in one host-scoped workspace, and publish only the document versions your team has reviewed.
One hostname, one workspace boundary
Your operating space and publication route stay connected.
This brings the Organization plan's workspace workflows to a managed tenant hostname. It is not a separate deployment, database, or storage bucket, and a browser cookie cannot switch the host into another workspace.
- 01your-team.docaccessible.comManaged organization hostname
- 02Private team workspaceMembers, roles, documents, sites, Program, jobs, and Exchange
- 03Optional public directoryOnly explicit, release-ready, exact-version publications
Signing in on the tenant hostname resolves the workspace from the host itself. Team members cannot use the workspace selector to cross that tenant boundary.
Connected workflows
Your portal does not lose the workflows your team already uses.
Invitations, notifications, vendor routes, and secure delivery links use the active organization hostname. Every record still follows the existing workspace role, entitlement, and audit rules.
Website PDF monitoring
Inventory PDFs across verified websites, flag source changes, and convert selected discoveries into private remediation drafts.
See the workflowVendor handoff with Exchange
Invite an external vendor into a case-scoped route, compare returned revisions, approve one file, and send it through controlled delivery.
See the workflowRequests and reader feedback
Route internal requests through Program Management and turn public accessibility feedback into assigned resolution work.
See the workflowPrivate work, deliberate publication
A hostname never makes a draft public.
Public access is a separate publication record. It identifies one reviewed document version and never follows the changing current draft automatically.
- 01
Reserve the hostname
An owner or administrator claims one available managed subdomain for the workspace. Retired names are not recycled to another organization.
- 02
Bring the team inside
Invite members, assign roles, and use the tenant hostname for authenticated document, monitoring, Program, review, and Exchange work.
- 03
Review an exact version
Complete the release checklist and record human evidence against the immutable version intended for publication.
- 04
Publish deliberately
Choose the public path, publish the reviewed version, and later republish or withdraw without exposing private workspace files.
Clear product boundary
Managed subdomain, not white-label infrastructure.
Included
- One managed hostname per Organization workspace
- Workspace roles and tenant-aware invitations
- The Organization-entitled workflows shown above
- Portal branding, directory, and indexing controls
- Exact-version publication and withdrawal
Not implied
- A customer-owned custom domain or DNS zone
- A separate application, database, or storage deployment
- Automatic publication of workspace documents
- WCAG, PDF/UA, ADA, or legal certification
- Remediation labor bundled with the subscription
Is this a custom domain?
It is a managed subdomain such as your-team.docaccessible.com. The Organization plan does not currently support a customer-owned domain or custom DNS zone.
Which DocAccessible workflows run on the portal?
The tenant hostname runs the workspace-scoped Documents, Program Management, website monitoring, feedback, review, jobs, Exchange, billing, API key, and webhook workflows included in the Organization plan.
Does reserving a portal make our documents public?
No. Workspace files remain private. An administrator must publish a release-ready immutable version before it appears through the portal, and the publication can later be withdrawn.
Will later edits replace a published document?
No. A portal publication stays pinned to the reviewed document version. A newer edit becomes public only after its own release evidence and an explicit republish action.
Can the public document directory appear in search?
An administrator can choose whether the public directory is enabled and whether search indexing is allowed. Indexable portals expose host-specific canonical metadata, structured data, robots guidance, and a sitemap for listed publications.
What happens if the workspace leaves the Organization plan?
Existing tenant pages remain readable, while new hostname claims, branding changes, and publications stop. Administrators can still withdraw a publication or retire the hostname.
Organization plan