Customer Portal
A portal where your clients accept proposals, sign contracts and find their invoices
Your clients accept the proposal and sign the contract from the links in your emails, and pay an invoice from the payment link you send. In a portal with your logo, they find their invoices, contracts and subscriptions, and sign in with an email code instead of a password.
Open your client portalFree account, no card needed.
- Free
- on every plan
- No passwords
- Email code or magic link
- 6 languages
- for clients and emails
FROM YOUR EMAILS
Your client acts from the email you send
Each step you send reaches your client as an email with a link. Your client opens it and does what you asked. There is no password to create.
-
Your client accepts the proposal from its link and confirms their email with a one-time code
-
They sign the contract from the signing invitation, without signing in
-
When a card is declined or the bank asks for approval, they pay from the link in the email, without signing in
-
What your client accepts, signs or pays shows on the proposal, contract or invoice in Enlivy
What can be different
What changes when your clients use the portal
Today you chase approvals, resend documents and answer requests about cards and plans. With the portal, your clients do these steps themselves.
| In the portal | Over email today | |
|---|---|---|
| Proposals | Your client reads the proposal, accepts it online and pays the first invoice once any contract is signed. | You send a PDF, wait for a reply and follow up on the first payment. |
| Getting paid | Your client pays the invoice by card from the payment link you send. | You wait on transfers and send reminders. |
| Card and plan changes | Your client changes the saved card, and changes, pauses or cancels a subscription when you allow it. | Requests like "change my card" or "pause my plan" land in your inbox and wait on you. |
| Documents | Contracts, receipts and e-invoices stay in the portal, and so do reports you share with a client. | Invoices in email, contracts in a drive, the rest hard to find. |
| Your brand | The portal carries your logo, and your own domain with the Custom Domain pack. | A third-party tool, or a plain email thread. |
| Your records | Each acceptance, signature and card payment shows on the client's records in Enlivy. | Exports, retyping and checking by hand. |
HOW IT WORKS
How to open the portal to a client
Your logo is already in Enlivy, so there is little to set up before you turn the portal on.
- Check your logo and choose the address
Your logo and icon come from Enlivy. Use the free Enlivy address, or add your own domain with the Custom Domain pack.
- Give a client access
Send a proposal or a contract, and your client opens it from the email. You can also open the portal to a client yourself. They sign in with a code by email or a magic link.
- Your client acts in the portal
Clients accept proposals, sign contracts, manage subscriptions and download documents.
- Choose what each client sees
You choose which sections a client can open and for how long, which documents and projects you share, and whether a subscription can be changed, paused or cancelled.
MAKE IT YOURS
Give clients a portal with your brand and domain
The portal carries your brand. Your developers can also place parts of it on your own website, such as the billing details form and saved cards.
-
Your branding:
the portal uses the logo and icon from your Enlivy settings.
-
Your own domain:
add one with the Custom Domain pack. You point the domain at Enlivy with a DNS record, and Enlivy checks it and sets up SSL. Until then, the portal uses its free Enlivy address.
-
Sign-in without passwords:
clients sign in with an email code or a magic link your team shares.
-
Private by design:
every client sees only their own invoices, proposals and contracts, and the documents you share with them.

SELF-SERVICE
What your clients can do in the portal
Clients see only what you allow. A section such as invoices or subscriptions appears in their menu once they have one.
- Proposals
- View proposals with their lines and totals
- Accept or reject online
- Fill in their billing details before paying
- Pay the first invoice by card or bank transfer
- Invoices & payments
- See all invoices, paid and unpaid
- Download each as a PDF or e-invoice file
- Pay an invoice by card from the payment link you send
- Manage their saved cards, which Stripe stores
- Subscriptions
- View active subscriptions and what is coming up
- Change the card a subscription bills to
- Change their options and see the new price before confirming, when you allow it
- Pause, resume, or cancel at period end, when you allow it
- Contracts
- View and download contracts as PDFs
- Sign online, one step at a time
- An optional email or SMS code before signing
- A notification and audit trail
- Documents & e-invoices
- Open the guidelines and playbooks you share with them
- Download them and see earlier versions, when you allow it
- Download their e-invoices: the XML, the PDF and, where the national system adds one, its signature file
- Reports, support & account
- Fill in, save as drafts and submit the report forms you open to them on a project, with the Reports pack
- Confirm a report your team wrote for them, when it asks for confirmation
- Write to your team from the Support page and attach files, when you give them access, with the Helpdesk pack
- Keep their billing details up to date, with a check that shows what is missing
API reference
Authentication sessions from the API
Create and retrieve customer-portal authentication sessions for your users, straight from the admin API. A session grants one of your organization's users scoped, time-boxed access to the customer application (the portal), authenticated by email, phone, or a magic link. Find the user, open a session (by ID or by email), then read it back.
Retrieve the users you can open a session for. Filter by email, run a free-text search, or page through the full list to find the right person.
/organizations/<organization_id>/users # filters: email, created_at_from/to, updated_at_from/to, ids, or q=... for free-text search
curl -G 'https://api.enlivy.com/organizations/<organization_id>/users' \
--data-urlencode 'page=1' \
--data-urlencode 'limit=20' \
--data-urlencode 'email=jane@acme.example' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json' const baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
// filters: email, created_at_from/to, updated_at_from/to, ids, or q=... for free-text search
const query = new URLSearchParams({
page: "1",
limit: "20",
email: "jane@acme.example",
});
const result = await fetch(`${baseUrl}/organizations/${organizationId}/users?${query}` , {
method: "GET",
headers: {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
},
}).then((response) => response.json());Open a session for a specific user by referencing their organization_user_id. This targets exactly one identity, so the session proceeds straight to authentication with no ambiguity.
/organizations/<organization_id>/user-client-portal-sessions curl -X POST 'https://api.enlivy.com/organizations/<organization_id>/user-client-portal-sessions' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"organization_user_id": "<org_user_id>",
"name": "Jane Doe",
"authentication_method": "email",
"permissions": [
"invoices",
"receipts",
"payment_methods"
],
"validity_hours": 72
}'
# Response includes: token, status, magic_authentication_url (for magic_authentication),
# authentication_verification_code (for email / phone), permissions, expires_at. const baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const result = await fetch(`${baseUrl}/organizations/${organizationId}/user-client-portal-sessions` , {
method: "POST",
headers: {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
"Content-Type": "application/json" ,
},
body: JSON.stringify({
// reference the exact user identity
organization_user_id: "<org_user_id>",
// required: display name for the session
name: "Jane Doe",
// how the user proves identity: email | phone | magic_authentication
authentication_method: "email",
// scope what the session may access in the portal
// options: invoices | receipts | network_exchanges | contracts | reports | payment_methods
permissions: [
"invoices",
"receipts",
"payment_methods",
],
// lifetime: set validity_hours OR expires_at (bounded by the server maximum)
validity_hours: 72,
}),
}).then((response) => response.json());
// Response includes: token, status, magic_authentication_url (for magic_authentication),
// authentication_verification_code (for email / phone), permissions, expires_at. Open a session by email instead of a specific id, handy when you only know the address. If the email maps to a single user, the session proceeds directly. If the same email belongs to multiple identities, the session is created in the awaiting_user_selection state and the user is prompted in the portal to choose which identity to authenticate as before continuing.
/organizations/<organization_id>/user-client-portal-sessions curl -X POST 'https://api.enlivy.com/organizations/<organization_id>/user-client-portal-sessions' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"email": "jane@acme.example",
"name": "Jane Doe",
"authentication_method": "email",
"permissions": [
"invoices",
"receipts",
"payment_methods"
],
"validity_hours": 72
}'
# Single match -> the session proceeds to authentication.
# Multiple matches -> status "awaiting_user_selection"; the user picks which
# identity to authenticate as in the portal before continuing.const baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const result = await fetch(`${baseUrl}/organizations/${organizationId}/user-client-portal-sessions` , {
method: "POST",
headers: {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
"Content-Type": "application/json" ,
},
body: JSON.stringify({
// reference the user by email
email: "jane@acme.example",
// required: display name for the session
name: "Jane Doe",
// how the user proves identity: email | phone | magic_authentication
authentication_method: "email",
// scope what the session may access in the portal
// options: invoices | receipts | network_exchanges | contracts | reports | payment_methods
permissions: [
"invoices",
"receipts",
"payment_methods",
],
// lifetime: set validity_hours OR expires_at (bounded by the server maximum)
validity_hours: 72,
}),
}).then((response) => response.json());
// Single match -> the session proceeds to authentication.
// Multiple matches -> status "awaiting_user_selection"; the user picks which
// identity to authenticate as in the portal before continuing. Read a session back: its current status, when it was last used, when it expires, and the user it belongs to. Poll the status to see the user move through authentication (including identity selection when the session was opened by email).
/organizations/<organization_id>/user-client-portal-sessions/<user_client_portal_session_id> # includes: organization_user, organization
curl -G 'https://api.enlivy.com/organizations/<organization_id>/user-client-portal-sessions/<user_client_portal_session_id>' \
--data-urlencode 'include=organization_user' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json'
# status: pending | email_verification_sent | awaiting_user_selection | success | expiredconst baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const userClientPortalSessionId = "<user_client_portal_session_id>";
// includes: organization_user, organization
const query = new URLSearchParams({
include: "organization_user",
});
const result = await fetch(`${baseUrl}/organizations/${organizationId}/user-client-portal-sessions/${userClientPortalSessionId}?${query}` , {
method: "GET",
headers: {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
},
}).then((response) => response.json());
// status: pending | email_verification_sent | awaiting_user_selection | success | expired Where it fits
Part of these setups
Each page follows one way of selling and shows what your client does, which features you use and what they cost.
- Agencies and studios Core Where your client accepts, signs, pays and finds every document, under your agency's name. See the setup
- Course authors Core Where clients sign their contracts, pay their invoices and find them again, under your name. See the setup
- Monthly billing Core Where your client pays, downloads invoices and manages their package, under your name. See the setup
- Sales teams Core The client's proposals, contracts, invoices and billing profile, under your name. See the setup
Works together with
- Contracts Write a contract, or let Enlivy draft it from your package's template when a client accepts your proposal. You send it, and your client signs online with an optional email or SMS code.
- Guidelines Document your best practices and policies, and keep your team aligned with clear, accessible guidelines.
- Helpdesk Website chat, client portal messages and email from your connected mailbox arrive in shared inboxes. Your team assigns and answers them, and reviews email from unknown senders.
- Invoices Issue an invoice and email it to your client. A card payment goes to your own Stripe account and the invoice is marked paid. A bank transfer you mark paid yourself.
- Network Exchanges Network Exchanges turns each invoice you issue into an e-invoice in the EU standard (EN 16931), ready to download. Where Enlivy is connected to a national e-invoicing system, today Romania's, it also sends and receives them for you.
- Payslips Your accountant works out the figures, and you record each amount in Enlivy on its own line, under your country's payroll code. Enlivy checks that the lines match the payslip's totals.
- Playbooks Write step-by-step procedures for the work your team repeats, with checklists, files and video, and keep them up to date as the work changes.
- Sales Pipeline See which leads are moving, read the last conversation before you follow up, and send the proposal from the lead's page.
- Reports Replace chat and email updates with reports your team fills in. Set the questions and how often in a Report Schema, and your clients confirm the reports written for them in your client portal.
- Receipts Record money in and money out, keep the payment file with each receipt, and let Enlivy issue the receipt when you mark an invoice paid with one of the payment methods you set for automatic receipts.
- Users Clients, suppliers, and colleagues share one list in Enlivy. Open anyone's record to see what they owe you or you owe them, their documents, reports, and proposals, as far as your role allows.
- MCP Connect Claude, ChatGPT, Cursor, or another MCP-compatible assistant to work with your invoices, contracts, and pipeline, within your own permissions.