Client Portals

How It Works

• One portal per NinjaCat account. Each NinjaCat account has a single Client Portal. All client users that have been invited to the portal can log in and view the content that's been published to it.
• You control what's visible. Only Agent-generated Artifacts (including any file types and static websites) and Data Apps that a NinjaCat user explicitly publishes to the portal are visible to invited clients.
• Clients log in securely. Invited users authenticate before they can see any content. And, they can be invited to more than one portal.

What Client Portals do not expose

Client Portals are intentionally scoped to published content only. The following information is never accessible to portal users, regardless of what has been published:

• Internal users — portal users cannot view your agency's internal NinjaCat users, their names, roles, or account access.
• Credentials and API keys — integration credentials, API keys, and any authentication configuration stored in NinjaCat are not exposed through the portal.
• Billing information — your agency's billing details, subscription information, and payment data are not visible to portal users.
• Cross-agency data — portal users see only the content published to the specific portal they were invited to. They cannot access data, reports, or artifacts belonging to other agencies or other client accounts.

Access & Permissions

PortalView is a user-level permission toggle that will need to be enabled for your internal user roles so they have access to Client Portals. When enabled for a NinjaCat user, that user can:

1. Access and view the Client Portals.
2. Invite client users to Client Portals.

If a user does not have PortalView enabled, they will not see the Client Portals and cannot invite clients.

Publishing Artifacts to a Portal

Agent-Generated Files & Static Websites

When an AI Agent generates a file, static website, or other artifact in a conversation, you can save it to an account using the Save to account… action on the artifact.

Clicking Save to account… opens the Save Artifact to Account dialog, where you choose the artifact's visibility:

1. Internal — the artifact is saved to the account and visible only to your team members with access to that account. It is not shown to Client Portal users.
2. Publish to Client Portal — the artifact is saved to the account and published to the account's Client Portal, so invited client users can see it.

Saving internally is the new option: you can now keep a finalized artifact associated with an account for future reference without exposing it to clients. Publishing to the Client Portal works as it always has. Either way, the artifact is also added to the account's Artifacts & Apps list, where you can change its visibility later.

📘

Websites: the Save to account… option becomes available once the site's build and deploy have finished. While a website is still being generated or deployed, there's simply nothing to save yet — nothing is discarded.

Note: any files generated prior to release for your org (broadly released to all orgs on 6/15/26) will not have a Save to account… option. The file would need to be regenerated if you wish to save or publish it.

Data Apps

Data Apps can also be published directly to a portal via their configuration settings:

1. Open the Data App and navigate to its Configure settings.
2. Click the Publish button.
3. Select the portal to publish to.

⚠️

Important — cross-account data visibility: When you publish a Data App to a portal, any data that Data App has access to across accounts will be visible in that portal. There is currently no account-matched filtering between portals. Review the Data App's data access scope carefully before publishing to a client-facing portal.

Data Apps you publish (or save internally) also appear in the account's Artifacts & Apps list in the Account Command Center, where your team can manage their visibility alongside all other account artifacts.

Viewing a Portal

Internal NinjaCat users can open a portal at any time to see exactly what clients see:

1. Open an Account's Command Center.
2. Click More Actions.
3. Select Open Portal.

From inside the portal, you and your invited customers can view all Data Apps and agent artifacts that have been intentionally published there. Internal users can also unpublish items directly from within the portal view.

Multiple accounts? Internal users can toggle between accounts they have access to using the account switcher at the top of the portal.

Customizing a Portal's Appearance

You can brand each client portal with your own colors and logos. Customization is available directly from within a portal.

Opening the Customize panel

From inside a client portal, select the customize icon at the bottom of the left navigation rail to open the Customize portal panel. (On mobile, open the navigation drawer and choose Customize.)

The customize icon only appears if you have permission to edit branding for the agency and/or the account.

Two scopes: Agency default vs. per-portal override

The Customize portal panel has two scopes, shown as a toggle at the top of the panel:

• Agency default — the org-wide branding applied across all client portals by default.
• Account Portal — an override for the individual portal you're currently viewing, layered on top of the Agency default.

Branding cascades account override → agency default → system default. In other words, a portal uses its own override where one is set, otherwise it falls back to the agency default, otherwise the built-in default.

To set your organization-wide default: switch to Agency default, make your changes, and save. These apply to every portal that doesn't have its own override.

To override a single portal: switch to Account Portal, tick the checkbox next to the element(s) you want to change, adjust them, and save. Only the elements you tick are saved as overrides — everything else continues to follow the agency default. To remove overrides and return a portal to the agency default, use the Reset to agency default link.

Color customization

You can recolor select portal elements. The panel offers two views:

• Basic settings — grouped controls covering the most common elements (page background and text, navigation background and icons, table/primary and secondary backgrounds and text, row hover, placeholder text, and a highlight color for buttons, tiles, links, and nav icons).
• Advanced settings — per-element control over the full set of individual color tokens, including a separate Mobile group for the mobile pop-out menu and profile icon.

Switch between them using the Advanced settings → / ← Basic settings link. Color values are entered as 3- or 6-digit hex codes, and your changes preview live in the portal as you edit. Selecting Cancel discards unsaved changes.

Logos

Portals support two independent logos:

• Organization logo — pulled through automatically from the company logo set in your Organization Settings. You can also upload a custom organization logo from the Agency default scope of the Customize portal panel.
• Account logo — the individual account's logo. By default the portal uses the account's own logo; from the Account Portal scope you can upload a custom logo for that portal, keep the account logo, or choose to show no logo.

Logo requirements:

• Supported formats: PNG, JPEG, WebP, or GIF. SVG files are not supported.
• Maximum file size: ~1 MB.

Custom portal title

You can also set a custom portal title (shown in the header). The default is Artifact Portal, with a maximum of 120 characters. Leaving it blank reverts to the agency default title.

Inviting Customers

Client users are managed from the Account Command Center:

1. Open an Account's Command Center.
2. Click More Actions → Settings.
3. Select the Account Portal tab.
4. Add the client users you want to invite.

Invited users will receive an email to accept the invitation and securely log in (their landing page: insightsportal.app). If a client is invited to multiple portals (across multiple accounts), they can toggle between those accounts at the top of the portal.

Note: Portal users do not appear in your overall NinjaCat User list. Portal users are managed separately from internal users.

Note: A user can only be invited to a Client Portal if they are not already a NinjaCat user.

FAQ

Can I have more than one portal per account? No. Each NinjaCat account has exactly one Client Portal.

Will my clients see everything in my account? No. Clients only see artifacts and Data Apps that have been intentionally published to the portal.

Who can invite clients? Any NinjaCat user with the PortalView permission toggle enabled.

How do I give a teammate access to manage the portal? Enable the PortalView permission toggle for a user role, and assign that role to the user. This grants them access to the portal and the ability to invite clients.

Can portal users see data across all accounts? Portal users see only what is published to the portal they are invited to. However, note that a published Data App may surface data from multiple accounts depending on its configuration — review the cross-account data warning under Publishing to a Portal above.

How do I unpublish something from a portal? Open the portal (Account Command Center → More Actions → Open Portal) and unpublish items directly from within the portal view. Only internal users with the PortalView permission can do this.

Can clients see our agency's internal users or account configuration? No. Client Portals do not expose internal users, their roles, or any account configuration. Portal users see only the content that has been explicitly published to the portal they were invited to.

Can clients see our agency's billing or other clients' data through their portal? No. Billing information and cross-agency data are not accessible through Client Portals. Each portal is fully scoped to the account it belongs to, and portal users cannot access data, reports, or artifacts from other accounts or agencies.

Can I save an agent artifact to an account without showing it to clients? Yes. When you save an artifact from an agent conversation, choose Internal in the Save Artifact to Account dialog. The artifact is associated with the account and visible only to your team — it is not published to the Client Portal. You can publish it later from the account's Artifacts & Apps tab.

Where can I see everything that's been saved or published for an account? Open the account's Command Center and go to the Artifacts & Apps tab. It lists every Document, Website, and Data App saved internally or published to the Client Portal for that account, with search and filters. See Artifacts & Apps.

Troubleshooting: the "Publish" button isn't appearing

If you're working with an AI Agent and don't see the button to publish an artifact to a portal, check the following, in order:

1. Account Portal must be enabled for your agency. The Publish button only appears when the Account Portal feature is turned on for your NinjaCat agency. This is an agency-level setting managed by an administrator (or your NinjaCat account team) — it is not something set per individual agent. If Account Portal is off, the Publish control is hidden entirely.

2. AI Agents must be enabled. The publish action lives inside the AI Agent chat experience. If AI Agents aren't enabled for your agency, you won't reach the screen where the button appears.

3. Check whether the button is just labeled differently. The same button changes its label depending on state: it reads "Publish…" before an artifact has been published, "Republish…" after changes, and "Published to [portal]" once it's live. If you see any of these, the button is present.

Note: Seeing the Publish button is controlled by the agency-level Account Portal feature, not by an agent's access level (Private / Can Chat / Can Edit / Owner). Agent-level access controls who can use or edit the agent itself — see Managing Agent-Level Access.

If Account Portal and AI Agents are both confirmed enabled and the button still doesn't appear, contact NinjaCat support — this is not a self-service configuration issue at that point.