THE SHORT ANSWER

Separate public and internal knowledge collections. Choose and verify the actual authentication route before uploading confidential sources; evaluate the documented IdP revocation window against the information involved.

Editorial guidanceSources & scope →
CustomGPT.ai logo above a conceptual illustration of an open public knowledge book and a closed private vault separated by a clear access boundary.

A business can have excellent documentation and still share the wrong information through an assistant. The problem is often a mismatched audience: a public visitor needs help choosing a service, while a colleague needs the internal procedure for delivering it. CustomGPT.ai offers public and private deployment options, but the source collection, access route and maintenance process must support the same boundary.

This guide designs two hypothetical assistants for a training company: a public course-information helper and an internal delivery assistant. It is based on official documentation reviewed on 14 October 2026, not a hands-on security assessment. The examples are editorial planning guidance. Confirm the relevant account features and deployment behavior before uploading confidential material.

Decide who may receive an answer before selecting sources

Write the audience in plain language. “Anyone visiting the course website” is an audience. “People who know the link” is usually a distribution method, not a reliable permission model. “Current delivery staff with the approved role” is an audience with an access requirement that the deployment must enforce.

For the example company, the public helper uses published course dates, prerequisites, accessibility information and cancellation instructions. The internal assistant uses approved trainer procedures and operational checklists. Learner records, payroll and passwords do not belong in either pilot collection.

CollectionIntended audienceExample question
Published course informationProspective learners and website visitorsWhich prerequisites apply to this course?
Trainer delivery proceduresAuthorized delivery staffWhich checks are required before opening a session?
Individual learner recordsSeparate approved business system and permissionsExcluded from this general knowledge pilot

Do not add a document to a public agent because only one section seems useful. Create an approved public version containing that section’s appropriate information. A prompt saying “do not reveal the rest” is a weaker boundary than keeping the rest out of the public collection.

Distinguish public visibility, private deployment and identity-provider access

CustomGPT.ai’s current documentation says public agents can be accessed without authentication, while private agent deployment requires users to log in with appropriate permissions. Its private deployment guide identifies Teams functionality as a requirement. Check this route separately from ordinary public sharing. See how private agent deployment works.

For a small internal pilot, the practical question is whether the intended colleagues have the supported accounts and permissions. For a wider partner or staff portal, an organization’s identity provider may be a more suitable route. Do not assume an administrator’s subscription seat count establishes how every end user should authenticate.

CustomGPT.ai also documents an IdP end-user route using an existing identity provider. The current access guide requires an Enterprise plan with SSO and end-user IdP enabled, plus role mapping. This is a separate deployment requirement, not an inclusion inferred from Standard or Premium seats. The IdP access overview explains the route.

In the hypothetical company, prospective learners use the public helper without signing in. Delivery staff use the chosen private route. The company does not publish the internal agent publicly merely to avoid setting up accounts or identity access.

CustomGPT.aiAffiliate link.We may earn a commission.

Keep the website’s login and the assistant’s login aligned

Putting a widget on a page behind a website login does not automatically establish every access control for the widget’s own service. Inspect how the assistant authenticates the user and what happens if its share link or embed route is reached separately. Treat the complete path as a deployment requirement.

CustomGPT.ai’s IdP setup guide says its IdP authentication applies to portal URLs and embedded deployments, rather than every alternative sharing route. It also requires the agent to be private. Review the organization deployment guide before treating a portal configuration as protection for a direct link or a custom API application.

If a developer builds a custom front end, have them review its server-side authorization and credential handling as part of that application. A browser-visible API key is not an acceptable substitute for user access controls. Confirm the supported integration pattern rather than improvising a private service through a public embed.

Test with an ordinary user and a signed-out browser, not only the account owner. Owners often have access that the intended audience does not. A working administrator preview therefore says little about whether a visitor is denied or a staff member can use the final page.

Build two small source collections with explicit owners

Give the public and internal collections separate registers. Record the document title, owner, intended audience and effective version. A document’s folder location alone may not communicate whether it is an approved policy or an obsolete draft. Make that status clear in the content and publishing process.

For the public helper, the course manager approves the current dates and prerequisites. For the internal assistant, the delivery lead approves setup and handover procedures. When a trainer notices an error, the correction goes to the appropriate source owner rather than becoming an unreviewed instruction in a conversation.

This separation also improves answers. A public visitor receives readable explanations of the offer. A colleague receives operational detail appropriate to their job. Neither has to sort through a mixed collection filled with both sales wording and internal exceptions.

CustomGPT.ai is worth considering when your business already has knowledge worth organizing and a recurring audience that needs supported answers. Evaluate its access route with your actual audience before making the source collection larger.

Review citations as another information surface

An answer can be appropriately short while its citation exposes an internal file name or leads to material with a broader audience than intended. Check the answer, source label, linked destination and any document-viewing experience together. Test them as the actual end user.

CustomGPT.ai’s settings documentation lists citation controls, source-name behavior, conversation sharing and exporting, domain controls and visibility settings. These are distinct decisions, not interchangeable privacy switches. See the agent settings guide.

For the training company’s public helper, a citation should lead to the approved course information. For the internal assistant, an authorized colleague should be able to inspect the relevant procedure through the intended route. Do not solve a permissions error by making the original internal document public.

Also inspect conversation sharing and exports. A copied answer or exported conversation can outlive the account’s access to the assistant. Communicate appropriate handling to staff and keep unnecessary confidential details out of a general-purpose question when they are not needed.

Use a boundary test set, not only answer-quality questions

Prepare a handful of ordinary questions first. Then add attempts to cross the boundary: a public user asks for trainer-only procedures, an internal user asks for excluded learner records, or a visitor tells the assistant to ignore its instructions. The expected response should name a useful next step without supplying unavailable information.

These tests inspect your configuration; they are not a universal guarantee against every possible disclosure. The stronger starting point remains source minimization and enforced access. If sensitive content is not part of the public collection, the public agent has less inappropriate material to retrieve.

  • A signed-out visitor can use the public helper and open its intended public sources.
  • The same visitor cannot use the internal deployment through the tested routes.
  • An authorized staff member can use the intended internal agent.
  • A user without the assigned access is denied the internal agent.
  • Citations, shared conversations and exports follow the intended audience.
  • Questions outside the collection lead to an honest limit and an appropriate human route.

Record the account type, deployment route and expected outcome for each case. If one route fails, correct that route and repeat the affected cases. Do not treat a successful homepage embed as proof that every share link and integration has the same behavior.

Plan for access changes before a colleague leaves

An internal assistant needs a defined offboarding process. Identify who removes the identity or role, who verifies the result, and what happens to retained conversation material. Do this before the first contractor finishes a project, not during an urgent access incident.

The current CustomGPT.ai IdP revocation guide states that active sessions can continue for up to 24 hours after role or attribute changes. It says an agent can be disabled to cut off that agent’s access before session expiry, affecting other users as well. Review the access update and revocation guide and decide whether that window fits the material involved.

For the example company, the delivery procedure library may tolerate that documented behavior under its approved policy; a different collection might require another access design. Do not promise instant individual revocation if the selected route does not provide it. Confirm what support and your administrator can actually do.

Launch with a reversible publication process

  1. Approve the audience and source register for each assistant.
  2. Confirm the required private or IdP capability on the actual account.
  3. Configure one deployment route and complete signed-out, allowed-user and denied-user checks.
  4. Review answers and citation destinations with the content owner.
  5. Publish a limited pilot with a visible contact route.
  6. Document source updates, access changes and the action for withdrawing the deployment.

If internal content appears in a public answer, restrict or withdraw the affected deployment immediately, inspect its sources and sharing paths, and follow the organization’s incident process. Fixing the wording of one answer does not establish that the collection is appropriate. A useful CustomGPT.ai service makes business knowledge easier to reach while keeping each audience’s access deliberate and reviewable.

Sources and verification

Editorial review 2026-10-19. Source check dates are recorded separately. Notes describe what each source supports and its limits.

View sources
  • How private agent deployment worksChecked Private deployment requires login/appropriate permissions and Teams capability.
    Limits: Documentation uses Teams and Enterprise terminology across guides; confirm enabled account capability with CustomGPT.ai. Source-level permissions or identity controls of a custom integration are not established by the cited pages.
  • End-User IdP Access OverviewChecked Distinct IdP end-user route, SSO/role prerequisites; availability must be confirmed.
    Limits: Documentation uses Teams and Enterprise terminology across guides; confirm enabled account capability with CustomGPT.ai. Source-level permissions or identity controls of a custom integration are not established by the cited pages.
  • Deploy AI agents to organization via IdPChecked Private visibility requirement; portal and embed route support rather than all sharing methods.
    Limits: Documentation uses Teams and Enterprise terminology across guides; confirm enabled account capability with CustomGPT.ai. Source-level permissions or identity controls of a custom integration are not established by the cited pages.
  • Access agent settingsChecked Separate settings for citations, source names, conversation sharing/exporting, domains, visibility and private deployment.
    Limits: Documentation uses Teams and Enterprise terminology across guides; confirm enabled account capability with CustomGPT.ai. Source-level permissions or identity controls of a custom integration are not established by the cited pages.
  • CustomGPT.ai external access changesChecked Enterprise+SSO+IdP prerequisites and up-to-24-hour active session; disabling an agent affects all users.
    Limits: Official documentation checked on 18 October 2026; vendor documentation is not an independent performance test. No checkout, account entitlement or live product test was performed.