Your team

The “Team” page, in the menu, gathers the members of your organisation and the access you open to others. Only the organisation's administrators see it.

On this page

Inviting a colleague

Click “Invite”, at the top of the page next to the number of members: the page goes down to “Invite a colleague”, below the list of members. Fill in their name, their e-mail, which will be their sign-in identifier, their role and their language; the phone is optional. Click “Invite”. Kedalia confirms: “Invitation sent: an e-mail lets your colleague choose their password.”

The welcome e-mail says the invitation comes from you, and for which team: its subject, “Julie invites you to Kedalia, for UX Tour”, and its first sentence, “Julie Morel added you to the UX Tour team on Kedalia…”, with the button right below. A colleague who already has a Kedalia account gets no second one: the e-mail tells them “Julie added you to the UX Tour team”, and they find your organisation in the selector at the top of the menu.

You do not choose their password. The welcome e-mail asks them to choose it themselves, with its “Choose my password” button, valid for 7 days. If their address is a Google account, they can also do without one and click “Sign in with Google” on the sign-in page. After 7 days, the “Forgot password?” link of the sign-in page sends them a new link. In the list, the “Password” column shows “To be chosen” until they have chosen it, then “Set”.

E-mail lost, in the spam folder or expired? While the column shows “To be chosen”, the envelope icon on their row, “Send the welcome e-mail again”, sends them a new one once you confirm, with a fresh link valid for 7 days. It no longer shows once they have chosen their password, nor for a disabled account. Three welcome e-mails an hour at most to one address, the invitation included: beyond that, the invitation is refused; invite again an hour later.

Roles

Below the choice of role, the form recalls what each one allows.

A “Member” sees all of the organisation's applications and improves them with the assistant as you do; they delete the applications and test versions they created, not their colleagues' — but deleting an application takes all of its test versions with it, their colleagues' included. An “Organisation admin” does the same, also manages the team and the organisation's settings, and can delete every application and test version of the organisation. The organisation's settings: its name, the support access and the access to the code on this page, the applications' artificial intelligence and the “Applications” tab of “AI usage”, and “Change only through a test version” in an application's settings.

Everyone finds their role under their name, at the bottom of the menu: click it to read what it allows. A member, who does not see the “Team” page, also reads there that the team and the settings are managed by the organisation's admins.

To change a colleague's name, language or role, click the edit button at the end of their row, then “Save”. When they leave the team, untick “Active account”: they can no longer sign in to your organisation, their row turns “Inactive” and their seat is freed.

The number of members

At the top of the page, a line says how many active members the organisation has, how many your tier covers, and the name of that tier. The number of seats depends on your tier. When they are all taken, the “Invite” button is greyed, the invitation form disappears, and a message under the number of members says so: change tier to invite more colleagues, or make an account that is no longer used inactive. Making an inactive account active again takes a seat too.

Kedalia support access

Depending on your tier, the page shows the “Kedalia support access” block. On that tier, the Kedalia team has no access to your applications. When you ask it for help with one of them, click “Allow support for 72 hours”: a dialog says what support will be able to do for 72 hours — open your applications, read your conversations with the assistant and their code, and act on them like an administrator of your team. Confirm with “Allow support for 72 hours”, or click “Cancel” to keep access closed. Once open, the page shows until when, and access closes by itself after 72 hours.

While it is open, “Renew for 72 hours” pushes the end back, and “Close now” closes it at once, without a dialog. Closed, the block says so: “Closed: Kedalia support has no access to your applications.”

Read access for your developer

Depending on your tier, the page also offers “Read access for your developer”: read access to the code of all your applications, with their whole history, so that a developer or contractor of your choice can get a complete copy whenever they want. Click “Open the access”: a window first says what will happen — a read-only account created for your organisation at your address, an e-mail to choose its password, and the login and password to give to your developer. Confirm with “Open the access”: the page then shows the identifier of this access. “Close the access” deletes it, after a confirmation: your developer can no longer get the code. You can open it again later, with a new password. To get your applications yourself, see Exporting.