# Give a customer organization a portal

Source: https://frosvo.com/docs/customer-portal
Updated: 2026-11-12

Let the people in a customer organization sign in to see their requests and progress, and let their approvers approve or decline things you ask for, with a record kept in the conversation.

The customer portal gives the people of a customer organization their own place to see what you are doing for them and to make decisions that need their sign-off, for example approving a quote. It builds on [customer organizations](/docs/customer-organizations).

## Before you start

The customer needs to be in an organization (Contacts → Organizations), and each person you want to give access needs an email address. You need the contacts permission to give access. Your workspace must be able to send email.

## Steps

1. Open **Contacts → Organizations** and open the organization.
2. Next to a person, choose **Portal: can see requests** or **Portal: can approve**. Choosing a role sends them an email with a sign-in link. Choose **No portal access** to take it away.
3. Share the portal address shown under the people list. It looks like `https://your-app/org-portal/your-workspace`.
4. To ask for a decision, open a conversation with someone from that organization, expand **Ask for approval**, say what needs approving, add details and a deadline (1 to 30 days), and choose **Ask for approval**. Their approvers are emailed.
5. Approvers sign in, open the request and choose **Approve** or **Decline**, with an optional comment. A note appears in the conversation: who decided, what, and when.
6. To withdraw a request nobody has decided, choose **Withdraw** in the same panel.

## What people see

After signing in, a person sees their organization's name, the requests from everyone in it (a short title taken from the first message, open or closed, the progress card and the next promised update), and the approvals with their status. Nothing from other organizations is shown, and the portal does not show message text, internal notes or contact details of colleagues.

## Writing from the portal

Everyone with portal access can **Start a new request** from the top of the page, and can **Reply** under any request they started themselves. They write through the same pipeline as your chat widget, so the message reaches your inbox like any other, with the usual limits, assistant and notifications, and the team's answers come back by email and show in the portal's progress. A person can only write in their own requests, never in a colleague's, and replying to a closed request reopens it.

## In their language

The portal, including the sign-in page, speaks the language of the person's browser: English, Spanish, French, German, Portuguese, Italian, Dutch, Turkish, Chinese, Arabic and Urdu, with right-to-left layout for Arabic and Urdu. Anything your team wrote (request titles, progress notes, approval texts) is shown as written.

## Safety and control

A sign-in link works once and lasts 15 minutes; it should not be forwarded. Opening it only shows a Continue step, so an email scanner or link preview cannot use it up, and after the person presses Continue it is spent for good. Sessions last 12 hours and are checked against your records on every page, so removing someone from the organization or taking their role away ends their access at once. Moving a person to another organization also removes their role. A decision can only be made from the portal itself. Only approvers can decide, only while the request is pending and before its deadline.

## Common problems

- **A person did not get the link.** They have no portal role, the address is different from the one on their contact, or the email went to spam. Ask for a link again after 15 minutes.
- **You cannot ask for approval.** The customer is not in an organization, or nobody in it has the approver role.
- **An approver sees "Only an approver can decide".** They have the member role. Change it in the organization.

## Related

See [customer organizations](/docs/customer-organizations), the [inbox](/docs/inbox), the [customer progress card](/docs/customer-progress-card), [contacts and campaigns](/docs/contacts-campaigns), [privacy](/docs/privacy) and [email campaigns](/docs/email-campaigns).

## Common questions

### Who can sign in to the portal?

Only people in a customer organization whom your team gave a portal role (member or approver) and who have an email address. They sign in with a link sent to that address; there are no passwords.

### What can a member see?

The organization's requests with their status and progress card, and the approvals asked of the organization. Members cannot decide anything. They never see messages, notes or people from other organizations.

### Can an approval be changed after it is decided?

No. A decision is recorded once with who made it and when, and the team is told in the conversation. A request nobody decided can be withdrawn by your team, and one past its deadline can no longer be decided.

### Can I find out who is a customer by trying email addresses on the portal?

No. Asking for a sign-in link always gets the same answer, whether or not the address has access, and links are only sent to addresses you gave a role.
