Manage customer workspaces in a partner portal

A partner portal lets your team create customer workspaces, allocate seats, and review usage under one enterprise agreement. The Honen team creates your portal and sets its seat pool, compute limits, and included features.

Open your portal

1. Sign in with the email address that received your portal invitation.
2. Open the workspace switcher from your account menu.
3. Select your partner portal.
4. Accept the invitation if prompted.

The switcher shows portals you can access. Portal access does not automatically make you a member of each customer workspace. Select a customer workspace in the switcher when you also have workspace membership.

Understand portal roles

Only the Honen team can change the contracted seat pool, compute limits, and included features. Portal roles and customer workspace roles are separate.

Create a customer workspace

1. Open Workspaces.
2. Select New workspace.
3. Enter the workspace name and the customer's administrator email.
4. Set the number of seats to allocate.
5. Set Allow seat overages if your agreement permits extra seats.
6. Open Compute limits to set monthly hours, concurrent sessions, or allowed GPU types.
7. Select Create & send invitation.
8. Check that the workspace appears in the list.

The customer receives an invitation to become the workspace owner. Allocated seats cannot exceed the portal's seat pool. Extra seats use enterprise billing; the portal does not collect card payments.

Change workspace access and seats

1. Open the workspace from Workspaces or Reports.
2. Select Workspace settings.
3. Change the seat allocation, overage setting, or active status.
4. Select Save changes.
5. Check the updated workspace status and seat count.

Pending invitations use seats. Before you disable overages, allocate enough seats for current members and pending invitations. Inactive workspaces keep their members, data, and seat allocations. Reactivate a workspace in the same settings dialog.

Set compute limits

Each customer workspace has its own compute allocation. The portal contract sets the maximum for each workspace, not a shared compute pool. Administrators and workspace managers can set lower limits when they create a workspace or open Workspace settings.

1. Open Compute limits.
2. Set monthly runtime hours and GPU hours.
3. Set concurrent session limits and GPUs per session, if required.
4. Select the allowed GPU types.
5. Select Save changes, or Create & send invitation for a new workspace.
6. Open the workspace's Compute page to check its limits and usage.

A blank field uses the portal maximum. Zero blocks new usage for that resource. Monthly compute limits reset on the first day of each month in UTC. GPU hours count each GPU separately. Two GPUs running for one hour use two GPU hours.

Compute limits apply before new sessions start. They do not stop sessions that are already running. Seat overages do not bypass compute limits. Only the Honen team can raise the portal's contract limits.

The Compute page shows monthly usage, hardware usage, course usage, and the latest 100 sessions. Usage before compute tracking started is not included. These records are usage estimates, not invoices.

Set notebook activity limits

In Workspace settings, open Compute limits → Notebook activity. Set Notebook cell runs / learner / minute and Notebook workspace starts / learner / minute. Select Save changes, then reopen the settings to check both values.

Each learner has a separate limit within each workspace. The limits reset every minute. A blank field uses the portal limit if set. Otherwise, the defaults are 60 cell runs and 10 workspace starts per minute. Reusing a running notebook does not count as another workspace start. Changes apply to the next request. A higher limit can release a blocked learner without a new course publication.

The portal contract can set a maximum for each field. Customer overrides cannot exceed those maxima. The supported ranges are 1–600 cell runs and 1–60 workspace starts per minute. Monthly compute allowances and session limits still apply.

For enterprise workspaces outside a partner portal, Honen support uses Enterprise workspaces → Edit workspace → Compute limits → Notebook activity. This console requires platform administrator or super administrator access. Partner-managed workspaces use their partner portal's Workspace settings instead.

Manage workspace administrators

1. Open the customer workspace.
2. Select Manage admins.
3. Enter an administrator's email address.
4. Select Add admin.
5. Check the administrator list or pending invitations.

An existing member receives administrator access. A new person receives a workspace invitation. This dialog lists only administrators and their pending invitations, with 25 entries per page in each list. Removing administrator access keeps the person as a workspace member. You cannot remove the owner's access or the last administrator.

Review usage

1. Open Reports.
2. Select Daily, Weekly, Monthly, or Yearly.
3. Select a date in the required period.
4. Review learning hours, active learners, and course completions by workspace.
5. Select Export CSV to download the report.

Select a workspace name to open its details and usage. Use the top-bar breadcrumb to return to the report. Report periods use Eastern time, and weeks start on Monday. Learning time updates daily; seat counts show current usage.

Administrators can select delivery periods under Email reports, then select Save report delivery. Reports go to portal administrators after each selected period ends. These reports are usage summaries, not invoices.

Manage the portal

Use Portal team to invite teammates and assign portal roles. Use Audit log to review portal changes and the people who made them. Use Settings to rename the portal or upload its logo. Logos accept PNG, JPEG, or WebP files up to 2 MB.

Use the portal sidebar to move between sections. Each section has its own address. Refreshing the page keeps the selected section. The far-left rail lets partners return to their workspace views. Select Partner to return to the portal.

Join a workspace as partner support

Portal administrators and managers can select Join as partner support on a customer workspace page. This gives you temporary workspace administrator access without using a paid seat. The workspace must be active. If you already have a regular membership or pending invitation, remove it first.

The People list identifies your partner organization. Hover over your name or picture to see which organization manages the workspace. Select Leave support access on the workspace dashboard or portal workspace page when you finish. Removing a portal teammate or changing their role to Analyst also removes their partner support memberships. Support access ends if the workspace leaves the partner organization.

Customer Success staff can also select Leave support access on the workspace dashboard or their workspace console. Leaving removes current access. It preserves learning history and does not change billed seats. If you leave support access in another workspace, your active workspace stays selected.

View detailed analytics

Open Analytics in the portal sidebar for the combined view across all customer workspaces. Open a customer workspace for the same analytics view limited to that workspace. You do not need to join a workspace to view these analytics. Analysts have read access.

Use Activity to search events and open member activity. Use Overview for usage totals, trends, member rankings, group totals, messaging channels, and activity types. Select a date range, group, or member to narrow the results. The combined view counts each active user once, even when that user belongs to several customer workspaces.

Clone a course into a customer workspace

1. Open the destination workspace in your portal.
2. Select Clone course.
3. Search for a course that you own or can edit.
4. Select the course.
5. Select Clone into workspace.
6. Wait for the confirmation. Large courses can take several minutes.

The destination must be active and have a customer administrator who has accepted their invitation. The copy belongs to that administrator. Temporary support members cannot become its owner through this action. The copy includes course content, media, settings, and revision history. It does not copy learner records or source editor access. If access changes during a copy, the system checks access again before it completes the copy. If copying fails, the dialog keeps the error visible. Correct the problem before you retry, or select another course. If the source requires publishing approval, complete that approval first. Missing source files must be restored before copying.

Use GPU instance presets

In Compute limits, select 4 × T4, 4 × A100, or 8 × A100. The preset allows that GPU type and sets the maximum GPUs per session. Save the workspace settings to apply the change. Presets that exceed the portal contract are disabled. Monthly quotas still apply.

These presets also appear in standard workspace compute settings and the full-sandbox project editor. In the project editor, the preset selects the hardware for new sessions. Hardware availability depends on Modal capacity. Notebook projects continue to support one T4 or one L4 GPU.