Skip to content

Popular

  • Embed not showing on my website
  • Connect Claude or ChatGPT (MCP)
  • Set up a custom domain
  • Order a build through Lumina
  • What Lumina Assistant can do

↑ ↓ to move · Enter to open · Esc to close

Clients

Collect logins and API keys

Ask a client for a password or key and receive it encrypted, without email or chat.

Most builds need the client's logins: their website host, domain registrar, Google Business Profile, booking system, or an API key. Do not collect them by email or text. Ask for them in Lumina and your client hands them over in their portal, encrypted. Only your team can open them, and every opening is recorded and shown to the client.

What you can ask for

  • Login: a username or email and a password.
  • API key: a key or token.
  • Secure note: anything else, such as a door code, recovery codes, or "I added you as a manager".

Let Lumina suggest what to ask for

Not sure what a build needs? On the client's Access card, press Suggest what to ask for. It opens the onboarding designer for that client. Lumina reads their deals and lists the access the build needs under Access we'll request. Remove what you do not want, and press Create form (or Rebuild form). Each ask is added to their Access page in the same step.

Lumina picks from a list of common asks, each with a note telling the client the safest way to share it:

  • Domain registrar login
  • Current website admin login
  • Google Business Profile access (add us as a Manager, no password)
  • Google Analytics and Search Console access
  • The calendar bookings should go into
  • Phone carrier account and port-out PIN
  • CRM login or API key
  • Customer or lead list export
  • Email marketing platform login
  • Texting provider API key
  • The email account automations send from
  • API keys for the tools to connect
  • Payments account (a read-only key)
  • Google Ads account access and Meta Business Manager access (no password)
  • Social account logins and review site logins
  • Code repository access, Apple App Store Connect access, and Google Play Console access
  • Hosting or cloud account

It only asks for what the services on the client's deals need. If the client was already asked for something under a similar name, it is not asked for twice.

A template designed with AI keeps its asks. When you apply it to a client's form with Replace with template, the asks are added to that client's Access page. See Onboarding forms.

Ask your client for a login or key

  1. Open the client from Clients and go to Access.
  2. Press Ask for a login or key.
  3. Fill in:
    • What do you need? (required), for example "GoDaddy login".
    • Where is it used? (optional), for example "To point the domain at the new website".
    • Note to them (optional), for example "Use an account with admin access."
  4. Press Add to their portal.

The request shows in the Access section of their portal as waiting on them. Send them their portal link if they do not have it. See Client portal.

What your client does

The Onboarding section of their portal shows "N logins or keys are waiting on you" with a link to Access, so they do not miss them while filling in the form.

In the Access section of their portal, your client fills in the item and saves it. It is encrypted when saved. They can also add things you did not ask for with Add a login or key, and replace an item later.

Your client can never see a secret again once saved, not even their own. They do see when your team last opened each item.

You are told by email, Discord or Slack when they hand something over.

Open a login or key

  1. Open the client and go to Access. Items read Waiting on them or Received.
  2. Press Open on a received item.
  3. Read the warning ("Opening this is recorded. Your client sees the date on their portal.") and press Open it.

You will see the username, password, key, and note, with copy and show/hide buttons. The secret clears itself after 2 minutes or when you close the window.

Remove an item

Press the trash icon on the item:

  • Withdraw removes a request they have not answered.
  • Delete it removes something they handed over. It cannot be recovered.

See the history

Press Show activity to see who asked for, handed over, replaced, opened or removed each item, and when.

Limits and permissions

  • Up to 40 items per client. Lumina and the MCP server can ask for up to 20 at once.
  • Asking, opening and deleting need Clients manage access. See Team and permissions.

If something goes wrong

  • "They have not handed this over yet." The item is still waiting on the client. Remind them, with their portal link.
  • "This one cannot be opened. Ask them to hand it over again." Withdraw it and ask again.
  • "Could not record that you opened this, so it stays closed." Opening is only allowed when it can be logged. Try again in a moment.
  • "That is the most this page can hold." You hit 40 items. Remove ones you no longer need.

More fixes are in Clients, portal and onboarding.

Still stuck? Ask Lumina Assistant in your dashboard (⌘J on any page), or read how to get help.