Handbook

Target information architecture and route map

The exact route syntax should adapt to the discovered framework, but the experience hierarchy should remain stable. Tenant context may use subdomains, path segments, or an authenticated context selector; do not duplicate…

Updated 2026-07-17

Public marketing site

/
/platform
/platform/adaptive-feedback
/platform/360-feedback
/platform/development-plans
/platform/analytics
/platform/engineering-leadership
/solutions/hr-and-people
/solutions/managers
/solutions/technology-leaders
/solutions/enterprise
/integrations
/security
/pricing
/customers
/resources
/company
/contact-sales
/sign-in

Primary: Platform, Solutions, Pricing, Resources, Security
Secondary actions: Sign in, Start free, Book a demo

Do not place every feature in the top navigation. Use a structured mega-menu only when there are enough released pages to justify it.

Customer documentation

/docs
/docs/getting-started
/docs/concepts
/docs/users
/docs/managers
/docs/hr
/docs/tenant-admin
/docs/global-admin
/docs/programs
/docs/question-library
/docs/360-campaigns
/docs/results
/docs/development-plans
/docs/imports
/docs/integrations
/docs/security-and-privacy
/docs/api
/docs/release-notes
/docs/troubleshooting

Docs navigation should support three entry models:

By role
By task
By concept

Every application page should have a contextual help link to the relevant docs page.

Authenticated workspace shell

Use one application with a workspace switcher, not unrelated “consoles.” Suggested workspaces:

My workspace
Manager workspace
HR workspace
Organization settings
Platform operations

Only show workspaces the person can access. Display the active tenant and active scope near the switcher.

Individual workspace

/app/today
/app/tasks
/app/feedback/give
/app/feedback/requests
/app/results
/app/results/:period
/app/development
/app/development/goals/:goalId
/app/imports
/app/notifications
/app/account/profile
/app/account/security
/app/account/privacy

Primary navigation: Today, Tasks, Results, Development.
Secondary navigation: Imports, Notifications, Account.

Manager workspace

/app/manager/overview
/app/manager/team
/app/manager/team/:personId
/app/manager/feedback
/app/manager/nominations
/app/manager/development
/app/manager/actions

Manager access to individual results and PDP content depends on policy and explicit sharing; the route existing must not imply data access.

HR workspace

/app/hr/overview
/app/hr/programs
/app/hr/programs/new
/app/hr/programs/:programId
/app/hr/campaigns
/app/hr/campaigns/:campaignId
/app/hr/participants
/app/hr/completion
/app/hr/reminders
/app/hr/insights
/app/hr/development-support
/app/hr/content
/app/hr/imports

Tenant administration

/app/admin/overview
/app/admin/organization/units
/app/admin/people
/app/admin/people/:userId
/app/admin/roles-and-scopes
/app/admin/invitations
/app/admin/import-jobs
/app/admin/authentication
/app/admin/domains
/app/admin/branding
/app/admin/frameworks
/app/admin/question-library
/app/admin/program-defaults
/app/admin/integrations
/app/admin/api-and-webhooks
/app/admin/data-governance
/app/admin/audit
/app/admin/billing
/app/admin/plan-and-usage

Global platform operations

/app/operator/overview
/app/operator/tenants
/app/operator/tenants/new
/app/operator/tenants/:tenantId
/app/operator/provisioning
/app/operator/plans-and-entitlements
/app/operator/billing-operations
/app/operator/catalog
/app/operator/framework-releases
/app/operator/feature-rollouts
/app/operator/regions
/app/operator/platform-health
/app/operator/delivery-health
/app/operator/integration-health
/app/operator/incidents
/app/operator/security-events
/app/operator/audit
/app/operator/support-access
/app/operator/release-management

External-rater flow

/r/:secureInviteToken
/r/:secureInviteToken/privacy
/r/:secureInviteToken/survey
/r/:secureInviteToken/complete

This flow should be low-friction, mobile-first, and independent of a paid subject seat. Account creation should be optional unless tenant policy requires authenticated raters.

Use nouns for destinations and verbs for primary actions.
Show no more than seven primary navigation items per workspace; group the rest.
Preserve the person’s current tenant and scope when switching workspaces.
Include breadcrumbs only where the hierarchy is more than one meaningful level deep.
Page titles describe the object or task, not the route implementation.
Use a global command/search surface for people, programs, campaigns, docs, and settings where authorized.
Never reveal a hidden workspace name in an access-denied message.
Mobile users get a simplified individual and manager experience; administrative bulk workflows may use responsive tables or explicitly state that a wider screen is recommended, but must remain accessible.

Capablio