> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vectorshift.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Learn what Portals are and when to use them in VectorShift

Imagine your credit risk team needs access to three agents and a financial knowledge base, nothing else. Or a client needs a branded interface with your loan eligibility chatbot embedded in their portal. A Portal is how you build that: a focused, deployable environment that contains exactly the tools, agents, and interfaces you choose, and nothing more.

Instead of giving someone access to your entire VectorShift organization, you give them a Portal. It has its own URL, its own branding, and its own access controls. You can open it in a browser, embed it in an external site, or share it with specific people. You can also assign a Portal as the default landing experience for specific members or teams, so they open directly into the right environment the moment they log in.

## When to use portals

Use a Portal when you want to give someone a ready-to-use experience rather than a building environment. Some common situations:

* **Internal tools for teams:** Build a Portal for your support team, finance team, or operations team with the specific agents and knowledge bases they need. They get a clean interface without any of the underlying complexity.
* **Client-facing products:** Deploy a Portal as a standalone product for a client. Brand it with their colors and logo, restrict access with a password or SSO, and embed it directly in their website.
* **Controlled access to agents:** You have built several agents but want different people to access different ones. Portals let you surface only the relevant interfaces to each audience.
* **Self-serve AI workspaces:** Enable workspace features so users can upload their own documents and query against their own knowledge base, all within your branded environment.