How customers sign in to your apps

Your customers sign in to your organisation’s public apps, never to the dashboard. They do it on the app’s own sign-in page, at the app’s own address, which shows your organisation’s name, logo and colour. You set the logo and colour under Settings.

An app is public when its audience is Anyone with its address. See Choose who can open an app.

In your customer’s language

The sign-in page and the mails your customers get are in English, Dutch or French. The page opens in the language of the customer’s browser, or in English when that is another language. At the bottom of the page they can choose another one, which the page then keeps.

The sign-in mail is in the language of the page the customer used, and that language becomes theirs. An invitation is in the language you choose when you send it.

The labels on this page are the English ones.

Sign in with a code

1. On the app’s sign-in page, the customer types their email address and chooses Email me a sign-in code.
2. They get a mail in your organisation’s name, with a six-digit code and a link. Replies to it go to your reply address, if you set one.
3. On Check your inbox, they type the code under Sign-in code and choose Sign in. Or they use the link in the mail and choose to continue.

The code and the link work once, for one sign-in, and expire after 15 minutes. There is no password.

The page tells nobody whether an address belongs to a customer: anyone who types an address sees Check your inbox, but only your customers get a code. Anyone else gets a mail in your organisation’s name, in the page’s language, saying what to do instead:

• No account yet, when the app lets anyone create an account: a button to Create an account.
• No access, when the app does not let people create an account: the address has no access to the app, and they can ask your organisation.
• A member’s address, or one you invited to join your organisation: a button that signs them in with kvyk.

These mails count towards the same limits as a code, below.

Members on a public app

Below the email field, a public app shows Member of your organisation**? Sign in with kvyk**. Members use their kvyk.ai account there, with one click when they are already signed in to the dashboard. An app for members only shows nothing else.

One sign-in for all your apps

A customer signed in to one of your public apps is signed in to your other public apps too: they open them without signing in again. This works within your organisation only: a customer of two organisations signs in to each one’s apps apart. On a domain of your own, a customer signs in once on that domain and stays there.

Signing out of one of your apps signs the customer out of all of them. They stay signed in for up to 30 days unless they sign out.

Let visitors create an account

When an app’s audience lets anyone create an account, its sign-in page shows New here? Create an account. The visitor types their name and email address, agrees to your privacy statement (the page links to it) and chooses Create my account.

They become a customer only once they have proven their address with the code or the link in the mail. Then they are on your People page, with a record in your Customers entity, and their consent is recorded: when they agreed, the words they agreed to in the language they saw them in, and your privacy link at that moment.

An address that belongs to a member of your organisation cannot become a customer: that person gets a mail with a button that signs them in with kvyk.

Until kvyk.ai opens to everyone, a visitor can create their own account only if kvyk.ai has let their address in. Anyone else is told kvyk.ai is not open yet and to ask you for an invitation. Customers you add or invite, and customers who already have an account, sign in as usual.

Invite a customer to an app

1. Open People, then the customer.
2. Under Invite to an app, choose one of your public apps and the Language of the mail, then choose Send invitation. The language starts at the one the customer last used, or English.

The customer gets the mail “Your organisation invited you to the app”, with a button that signs them in. It works once, within seven days; after that, they open the app and sign in with their address.

An app can also invite customers, for the member using it: for example a form where staff add a guest. That works when the member’s data roles let them add customers. Someone new is added as a customer then.

Consent the first time they sign in

A customer you added on the People page, or invited to an app, has not agreed to your privacy statement themselves. The first time they sign in, after the code or the link, the page Before you open the app asks them to. It shows the same words as when creating an account, with a link to your privacy statement. They tick the box and choose Continue to the app.

Their consent is recorded as for an account they create themselves: when they agreed, the words they agreed to in the language they saw them in, and your privacy link at that moment. Their record’s Consent and Consent given at are set too. They are asked only once, and without ticking the box they do not get in.

This step appears only when you set a privacy statement under Settings. Without one, the customers you added or invited sign in straight away.

Limits that protect sign-in

• A new code is sent at most once a minute for the same address, and so is a mail saying what to do instead.
• A customer can ask for five codes in 15 minutes, ten in an hour and thirty in a day. Past that, the sign-in page says how long to wait before trying again.
• Five wrong codes stop that code. Ten wrong codes within an hour stop codes for that address for an hour. The link in the mail still works.
• When very many mails go out for your organisation at once, sending pauses for a while.

What customers can see

Customers who sign in see and change only what the data roles you give them allow: usually their own records and the ones linked to them, such as their orders, and only the fields the role shows them. A customer who creates their account starts with your data roles for new customers. Without a data role, they see none of your records.

Customers withdrawing their consent

Each app has an account page, which your app can open for the person signed in. There a customer sees who they are signed in as and the devices they stay signed in on, and on a public app can choose Withdraw my consent. They are asked once more, then signed out of every app of your organisation at once, on every device. See Your apps on a phone for staying signed in. See Customers for what you see.

To sign in again, they ask for a code as usual. After the code or the link, the page asks them to agree to your privacy statement once more; when they do, they are signed in.

Removing or erasing a customer

When you remove or erase a customer on the People page, they are signed out of every app within seconds and can no longer sign in. See Customers.