Organisations

An organisation is an institution or a research group on Pangur. Each member holds one seat, and a seat gives that person the Institution plan’s allowances. The plan applies to everything they do, their own projects included.

Pangur sets an organisation up with its name, its number of seats and its first admin. To arrange one for your institution, get in touch.

Joining

There are two ways in.

• By invitation. An admin enters your email address and you receive a link. If you already have an account, signing in with that address accepts the invitation; so does opening the link. If you don’t, the link sets up an account for the invited address and emails you a link to choose a password. An invitation also lets you in while Pangur has a waitlist. Links work for 14 days.
• By email domain. Pangur verifies the domains an organisation owns, such as ed.ac.uk. If the organisation’s admins have turned joining on for a domain, anyone who signs in with a verified address there takes a seat, while seats remain.

If you sign in only with a Microsoft account, Pangur cannot be sure the address is yours, so neither an invitation nor a domain seats you by your address alone. Open the invitation’s link instead; it works whichever way you sign in.

You can belong to more than one organisation. Account lists the ones you are in, and Usage says when your plan comes from a seat.

Leaving

Choose Leave… beside the organisation in Account, or at the foot of the organisation’s page. Your seat is freed and your plan goes back to whatever you hold yourself. Your own projects stay yours.

Shared projects

A project can belong to an organisation rather than to one person. Choose the organisation under Belongs to when you make a new project. It stays with the organisation whoever leaves, and its address starts with the organisation’s handle, as in /p/edinburgh-history.letter-books/library.

Each person in a shared project has a role:

• Owner: everything an editor can do, plus choosing who else is in the project, renaming it and removing it. The organisation’s admins are owners of all its projects.
• Editor: adds and changes references, files, notes, highlights, catalogue records, arrangements, analysis and exhibitions.
• Viewer: reads, asks and exports. A line at the foot of the screen says so, and controls that would change the project are greyed out.

Everyone in a project shares its library, catalogue, arrangements, copies, transcriptions, analysis and exhibitions. Each person’s Ask conversations, research documents, drafts and topics are their own: nobody else in the project sees them. An item’s page says who added it and who changed it last.

To add people, open the project’s settings and go to Members. Members of the organisation are added straight away. Anyone else is sent an invitation and joins as a guest: an editor or a viewer on that one project, taking no seat and none of the organisation’s plan. A guest invitation lets a new person past the waitlist, as an organisation invitation does.

Owners also see Activity there: who changed the project’s shared work, what they did, whether on the web, in the app, from the CLI or through an assistant, and when. Ask conversations, documents and drafts are never listed.

If you are removed from a project, or leave it, what you added stays for the others. Your own conversations, documents and drafts there are kept for 30 days so you can export them, and then deleted. We email you to say so.

Exhibitions from a shared project are published under the organisation’s public handle, pangur.io/<handle>/<exhibition>. The organisation’s admins choose it on the organisation’s page; until then, its exhibitions cannot be published.

Removing a shared project does not remove its exhibitions. If it has any, the confirmation asks which of the organisation’s other projects (one you can edit) they move to.

For admins

The organisation’s page is at /organisation/<handle>, linked from Account. Admins see:

• Members, with each person’s role, how and when they joined, and when they were last active. Change a role, or remove someone. An organisation always keeps at least one admin, so the last one cannot leave or step down until someone else is made an admin.
• Invite people: one or more addresses, as members or admins. Inviting an address again sends a fresh link, and the old one stops working. Invitations still waiting appear under Waiting to join, where you can withdraw them.
• Joining by email address: the switch for each verified domain.
• Public handle for exhibitions: the handle the organisation’s projects publish under.
• Use in the last 30 days: each member’s Ask questions and model use, and what they hold in the organisation’s projects. Files in the organisation’s projects count against the organisation, not against anyone’s own plan.

Every seat counts against the organisation’s limit, admins’ included. When the seats are used up, invitations wait and domain joining pauses until a seat frees. Ask Pangur to raise the limit. Lowering it never removes anyone.

An archived organisation keeps its members, but their seats stop giving the plan and nobody new can join. Once it is archived, Pangur can delete it if you ask: its projects go with it, with their libraries and exhibitions, and so do its members’ seats and its public handle.