> For the complete documentation index, see [llms.txt](https://docs.scaleflex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleflex.com/portals/managing-a-portal/access.md).

# Access

You can make your Portal public or private, depending which method suits your use case best. 

## Public Portal

Publicizing your portal means users are not obligated to register to access it. 

Anyone can access your portal by simply sharing your portal link.

However, you can password-protect your Portal and grant it a start or expiration period for security. 

## Private Portal

Privatizing your Portal adds bonus security to the assets and information shared. 

You can allow users with the organization or the DAM to access the Portal or require external users to register and also be able to approve their access. 

When users register, you can delegate who in your company receives the user registrations to approve or disapprove them in the Portal. 

<figure><img src="/files/MBwOmqo31QpAPMVmE9Ta" alt="" width="375"><figcaption></figcaption></figure>

<br>

## Owner

You can view the current portal owner at the bottom of the Access page. \
The owner of the Portal has the right to remove themselves and nominate a new user as Owner of the Portal.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scaleflex.com/portals/managing-a-portal/access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.