Give your knowledge somewhere people actually find it.

A branded, searchable help center on your own domain, for customers, employees or partners, with answers grounded in what you published.

Portal overview for ATA in InteractiveDox: Live and Setup Complete, pages, versions and readers, the versions table with v1.1.1 Active in two languages, and the default approval workflow.

One portal at a glance: status, pages, versions, languages, readers, and the approval workflow it inherits.

API reference that stays true to the spec.

Every portal has a place for API specs. Register one, and the pages that follow it are rendered from the spec itself rather than copied by hand.

API specs for the ATA portal, version v1.1.1: 19 endpoints, 4 methods (POST, PUT, GET, DELETE), 3 sections grouped in the sidebar, 0 drifted, and a list of synced endpoints with their methods and paths; Refresh from spec and Import spec actions.
  • 01

    Import a spec

    Register an OpenAPI spec with a portal version. Its endpoints, methods and sections are read from the spec.

  • 02

    Pages that follow the spec

    Pages marked as auto-synced pull their content from the spec; when it changes, they re-render with the new endpoints, parameters and examples.

  • 03

    Drift, checked

    The portal reports how many synced pages have drifted from the spec, and when it last checked.

01

Your domain, your brand, your access rules

Custom domains, your branding, and single sign-on for private portals. The help site reads as part of your product, not a vendor page.

02

Change the next version without disturbing the current one

Work on the next version while readers keep using the current one, then switch when you are ready. Every language stays in step, including nine Indian languages.

03

People and AI get the same answer

Readers search, browse and ask questions answered from your approved content. The AI tools you allow read exactly the same pages.

From approved content to a help center people use.

A portal is not a place to park pages. It is where your customers and your people find the answer, and where you learn what they still cannot find.

01

Publish the guides, SOPs and training you already created, in one place.

02

Show each audience what they should see: customers, staff, partners.

03

See what people look for, what they read, and where they get stuck.

04

Let the AI tools you allow answer from the same current pages.

The specifics, stated plainly.

Publishing

  • Custom domains and full branding
  • Single sign-on for private portals
  • Versions with a draft → active lifecycle
  • Organize pages the way your readers think
  • Unlimited readers on every plan

Reach

  • Translation, including nine Indian languages
  • API reference with a try-it playground
  • Readers can ask a question and get a cited answer
  • The AI tools you allow read the same pages

Signals & upkeep

  • Reader analytics and search reports
  • Page feedback and suggested fixes
  • Broken links and stale translations flagged for you
  • Spelling, grammar, and writing-style checks

Documentation Portal questions, answered.

What are Documentation Portals?

Documentation Portals are public or private help sites for customers, staff, partners, and approved AI tools. Each portal can have its own versions, branding, pages, and access rules.

Can portals use our own domain and branding?

Yes. Portals can use your own domain, logo, colors, fonts, and access settings.

Do portals show what readers need?

Yes. You see what readers search for, what they read, what they say about each page, and where a page needs work.