Skip to content
PartnerPortal.io Docs

Other

The Other page brings together a few portal-wide essentials: your company details, a couple of admin controls, and — for portals with API access — your API keys.

Open it from Portal Setup -> Other.

Depending on your plan and permissions, you may see:

  • Company Info
  • Portal Setup
  • API Keys for portals with API access enabled

Company Info

Section titled “Company Info”

The Company Info card is where you update the core details tied to your portal.

You can edit:

  • company name
  • subdomain
  • custom domain
  • company domain
  • support email

These settings affect how your portal is identified and how partners find and recognize it.

Update company info

Section titled “Update company info”

  1. Open Portal Setup -> Other.

  2. In Company Info, click Edit.

  3. Update the fields you need to change.

  4. Click Save.

If you change the subdomain or custom domain, PartnerPortal may ask you to sign in again after the update.

If you enable a custom domain, your DNS should point a CNAME to ssl.partnerportal.io.

Portal Setup

Section titled “Portal Setup”

The Portal Setup card on this page contains two straightforward admin controls.

Show Quickstart Checklist

Section titled “Show Quickstart Checklist”

Turn this on if you want the Dashboard quickstart checklist to appear again for your internal team.

This is especially useful when:

  • you want to finish setup tasks later
  • a new owner or admin is taking over the portal
  • you want the checklist visible again after hiding it earlier

Disable Partner Notifications

Section titled “Disable Partner Notifications”

Use Disable Partner Notifications when you want to stop partner-facing emails from being sent from the portal.

When enabled:

  • partner organizations do not receive portal emails
  • partner users do not receive portal emails

This is a portal-wide control, not an individual user preference.

API Keys

Section titled “API Keys”

If your portal has API access enabled, this page can also include an API Keys card.

Use it when you need programmatic access to PartnerPortal for a custom integration, internal workflow, or automation.

From here, you can:

  • create a named API key
  • copy the client ID
  • copy the client secret when it is first created
  • revoke a key later if it should no longer work

If you are planning to build against the API after creating a key, start with Developer Documentation and Public API Guide.