Portals
Portals are branded places where users discover and connect approved integrations, skills, and MCP access.
Portals turn a Workforce setup into a user-facing experience. Create a portal for a customer, partner, department, or internal team, then publish the integrations and skills that group should use.
What you'll learn
- How admins build a portal
- How users experience a portal
- How access groups, integrations, skills, highlights, and authentication fit together
Portal journey
Admins create the portal and decide what appears inside it. Users open the portal, authenticate, and connect to the approved resources.
Create a portal
Open Portals from Workforce and create a portal with a clear name and description. Use the description to explain who the portal is for and what kind of work it supports.
Add access groups
Access groups decide which users can see each portal resource. Groups can apply to every account by default or match SSO group IDs.
After adding a resource, open the resource and explicitly allow the groups that should see it.
Add integrations
Publish integrations so users can connect approved tools. A portal integration can be:
| Listing type | Meaning |
|---|---|
| User-configured | Each user connects the integration with their own credentials |
| Pre-configured | Administrators manage the shared credentials and provider settings |
Add skills
Publish skills so users can run approved workflows. Skills can show linked integrations, which helps users understand what access powers the workflow.
Highlight starter resources
Highlights organize selected resources on the portal home page. Use them for recommended workflows, starter kits, or department-specific bundles.
Configure authentication
Portal authentication controls who can enter the portal. Configure SSO tenants, email or domain allowlists, and session expiry settings.
Users authenticate before they see portal resources.
Test the employee experience
Open the portal as a user and check the home page, integrations view, and skills view.
Magic MCP in portals
Portals can expose portal-aware Magic MCP access. Use this when users should connect MCP clients through a branded, authenticated surface rather than a project-internal endpoint.
Use portal-connected Magic MCP when:
- access should be user-specific
- the connection should honor portal authentication
- users need a branded entry point
- resource listings and requests should wrap MCP access