Pangur docsWork in an organisation
An organisation is a group that holds seats on the Institution plan and can own projects its members share. This page explains seats, admins and members, what is shared and what stays your own, and how joining and leaving work.
An organisation is a group, such as a research group or a department, that holds a number of seats on Pangur's Institution plan. Everyone with a seat has the Institution plan for as long as they hold it, and the organisation can own projects that its members work on together. Pangur's administrators create organisations, and the organisation's own admins run them from then on. Your organisations are listed on your Account page under Organisations, and each has a page of its own.
Seats and the Institution plan
A seat is one person's place in the organisation. A new organisation has 5 seats, and Pangur raises the number on request. While you hold a seat in an organisation that has not been archived, your plan is Institution whatever plan you had before, and the organisation is named on your usage page. Your personal projects remain yours and keep working as they did. What the Institution plan allows is set out in Plans, limits and usage.
Once every seat is taken, nobody new can join. Invitations wait until a seat is free, and an attempt to add a member is refused with a message naming the organisation and its seat count, which suggests removing a member or asking Pangur to raise the limit.
Admins and members
Everyone in an organisation is either an admin or a member. Every member can see the organisation's name, its admins and their own seat, and can leave. Admins can also manage the members and their roles, send invitations, switch on joining by email domain, see each member's use and choose the organisation's public handle for exhibitions. Those tasks are described in Manage an organisation.
An organisation always has at least one admin, so the last admin cannot leave or step down until someone else has been made an admin.
Organisation projects
An organisation can own projects, which its members share. This is not offered on every account or deployment. If yours does not offer it, Pangur says that organisation projects are not available yet and only personal projects exist; the rest of this section assumes they are.
Any member with a seat can create a project for the organisation by choosing the organisation under Belongs to in the New project dialog, and the person who creates it becomes its first owner. An organisation can have 5 projects for each seat, and these do not count against anyone's limit of 12 personal projects (see Projects and libraries). An organisation project's address starts with the organisation's handle followed by a dot, for example /p/keith-group.letters.
Holding a seat does not, on its own, open every project in the organisation. You can open an organisation project if you have been made a member of that project, as an owner, editor or viewer, or if you are an admin of the organisation, since admins open every one of its projects as owners. Someone who cannot open a project is simply told that it does not exist. A project's owner can also invite someone from outside the organisation as a guest, with the editor or viewer role. A guest does not take a seat and does not get the Institution plan. The details of membership are in Project members and roles.
What is shared and what is your own
In an organisation's project, the work on the library is shared and the work of thinking and writing stays personal. The project's settings put it this way: "Everyone here shares the library, catalogue, analysis and exhibitions. Conversations, documents and drafts are each person's own."
| Shared with everyone in the project | Personal to each person |
|---|---|
| The library: items, files, notes, collections | Ask conversations |
| The catalogue and arrangements | Research documents in Research |
| Analysis: corpora, readings, corrections | Drafts in Plan and Write |
| Exhibitions | Topic labels on highlights |
Members can see who added and who last changed each item, in the library list's "Added by" and "Modified by" columns and in each item's history. The project's Activity, which only owners and admins can see, lists the changes to the shared work: who made each one, what kind of change it was, which surface it came from (the web, an app, the command line or an assistant), and when. Because Ask conversations, documents, drafts, topic labels and exports are personal, Activity does not list them.
Model use is counted against the person who does the work, so a question you ask or a source you analyse in an organisation's project counts against your own allowance. A few kinds of background work are charged to the project's owner instead (Models, assistants and who pays).
Storage in organisation projects
Files in an organisation's projects count against the organisation's storage, which is pooled: the Institution plan's storage allowance multiplied by the number of seats. With the default allowance of 20 GB per seat and 5 seats, the pool is 100 GB. Files in your personal projects still count against your own allowance. When an upload would take the organisation past its pool, Pangur refuses it and suggests removing something or asking an organisation admin about more seats.
Joining an organisation
You can join by invitation, by email domain, or automatically at sign-in.
When an admin invites your email address, the email links to a page headed "Join" and the organisation's name. If you already have a Pangur account, choose I have an account: sign in to accept. If not, the page offers to set up an account for your address: give your First name and Last name, choose Set up my account, and follow the email Pangur sends. Invitations last 14 days.
If the organisation's admins have switched on joining for your institution's domain, you take a seat the moment you sign in with a verified address at that domain, with no invitation needed. More generally, whenever you sign in with a verified, proven address, Pangur accepts any invitations waiting for that address, whether to organisations or to projects.
As with shares, a sign-in through Microsoft or GitHub alone does not prove your email address. If that is how you sign in, open the link in the invitation email instead; it still works.
An invitation page can also tell you that the invitation has expired, in which case you should ask the person who invited you for a new one, or that it could not be found, has already been accepted or cannot be used. The same page handles invitations to a single project as a guest, which say whether you join as an editor or a viewer.
Leaving an organisation
Open the organisation's page, choose Leave…, and confirm with Leave the organisation. Your seat is freed, your own projects stay yours, and your plan returns to the one you would have without the seat.
Leaving, or being removed by an admin, also removes you from the organisation's projects, apart from any you were added to as a guest. If you are the last admin you cannot leave until someone else has been made an admin.
What happens to your work when you leave a project
When you leave an organisation project, or are removed from it, the shared work stays in the project. Your personal work there (your Ask conversations, research documents, drafts and topic labels) is kept for 30 days. Pangur emails you, and during those 30 days you can still export your own work from your Account page (Export your work or delete your account). After 30 days it is deleted.
Archived organisations
Pangur's administrators can archive an organisation. Its page then says "Archived. Seats no longer give the Institution plan, and nobody new can join." Its projects stay readable, but everyone opens them as a viewer, and no new projects can be made in it.
Share references
A share gives named colleagues read access to one or more references from your library, with their files and notes. This page explains how to create a share, what the invited person sees, and how a share differs from other ways of giving access.
Project members and roles
Members of an organisation's project are owners, editors or viewers, and guests from outside the organisation can be added too. This page explains what each role can do and how to add, change and remove members.