People and access, one question at a time.

In the organization choose Settings, Administration, People, Invite by email…; in a space, Invite to this space…. Write the address and choose what they will be able to do, and the mail is sent by Fallthere, with a single sender. Whoever is invited finds the invitation on entering, even without an account: the account is born with the invitation, and Enter accepts it.

In the organization you choose Member, who works in the organization, or Guest, who sees only what is opened to them: guests are admitted in General, under Who joins. In a space you choose Edits (reads, writes and creates), Comments (reads and leaves comments) or Reads (without changing anything). An invitation never gives “Manages”: the database rules forbid it too.

By default whoever administers, or whoever has the “Invite” permission; in Settings, Administration, General, under Who joins, the organization can let every member invite. Whoever cannot knows before writing an address, and finds Ask whoever administers and Who can do what. In a space, whoever can share it invites.

In the organization the base roles are Leads, Administers, Member and Guest; on a page or in a space they are Reads, Comments, Edits and Manages. Roles of your own are written by whoever administers, in Settings, Administration, Roles: a name, a mandatory description and the capabilities you choose, for example an “External reviewer” who can read, comment and export.

Nine: read, comment, edit, create inside, move to the trash, share, export, use Pan and read reserved fields. Ticking one ticks the others it needs: with “share” come “edit”, “comment” and “read”.

Whoever manages it, that is whoever has Manages on the page or on the space: in the sharing window they have Add someone. Whoever sees it and does not manage it finds Ask to add someone: the request goes on its own to whoever can share, who decides.

In the sharing window choose the person, What they will be able to do and For how long: forever, a week, a month. Next to the name the date the access ends appears, and on that date it ends. Marta, for example, gives Davide a week of access to a page.

In the sharing window open More, choose the person under What would they see…? and press Look: the answer is in words, for example “Can read and export; cannot edit”. The database gives it, capability by capability.

Open Share (on a page, then Who sees it): in the list tap Change next to the name and then Remove. A timed access ends on its own on the date. Every grant stays written in the log, with who, which and when, never the content, and a line once written is not changed or removed.

First it tells you who will see it, for example “The 12 people in Sales will see it too. Move it?”. Where you cannot, it says “Not here” and why.

You find Ask for access. In a by-request conversation everyone sees the name and no one the messages: whoever wants in asks, and the request reaches the owners in Now.

Whoever has the “read reserved fields” capability. Without it the column does not even arrive: it is not hidden by the screen, it is not sent.

Open Teams, from the organization’s menu or from Settings, and choose New team. In Who is in you put the people, in Where it works the spaces open to the team, with what it can do and until when. The team’s space is born with the team and is named after it.

A team is a group of people and has its own space, born with it: joining the team means joining the space, and leaving means leaving it. A space is a place where pages live, open to whoever you choose.

Whoever administers, or whoever leads the team, as the database decides.

In Management, the tab of the People table for whoever manages people (you open it with Open the people): who is about to join, with Postpone and Withdraw, then a row per person with name, role and spaces. Postpone renews the invitation and sends it again, at most once every ten minutes.

In the People table: Reports to is a graph from top to bottom, with the photo above the name, and By team has the same drawing. Title and “Reports to” are written by whoever administers; on the phone it becomes an indented list.

With the welcome: a document with the steps a newcomer takes one at a time, in Settings, Administration, Welcome. It can be for everyone, for a team or for a role: a team’s wins over the role’s, and the role’s over everyone’s. See Onboarding.

To enter a space yes, but the invitation creates it. For a call with a link, a form or a booking no: those are public pages, and the guest sees only that.

Only the room: the faces, the screen, the questions, the notes. They do not see conversations, spaces, whiteboards or Pan. Copy a link to join takes guests to a public page, and the link lasts twelve hours and can be cancelled.

You send the link: the page is public, has your organization’s colors and font, and whoever answers does not need an account. A form’s answers are rows of a table, which whoever has access to the table sees; a booking arrives as a request that you Confirm or Decline, unless the page confirms on its own.

If the person who made them shows them to the team, in the People table, with their name and their face in place of the photo, and in the org chart under that person. Who sees an agent, only you or the team too, is chosen when you prepare it.

In the CRM: they are marked “Outside”, they are neither members nor agents, and a single search finds them by name, domain or email. When someone writes to you, Add to people… puts them among the contacts.

Yes. An app gives a six-digit code and, if you turn it on from the Profile, signing in needs that code too. Whoever leads the organization can ask everyone to use it: in Settings, under Administration, General has the Security section with the box Ask everyone to use two-step verification. Whoever does not have it turns it on at the next sign-in, and whoever has it cannot turn it off.