Skip to content
PalmaPlan — the wiki ← PalmaPlan

Sharing and roles

Inviting someone onto a schedule, choosing what they can do with it, what happens on the invitee's side — who accepts or declines —, and how to leave a schedule shared with you.

Inviting

From Settings › Sharing — a tab the owner and the schedule's administrators see —, the MEMBERS section lists who has access (the owner marked owner, each member with their role). Right below, INVITE offers a role menu — Administrator, Contributor or Reader, each saying in one sentence what it allows — and an E-mail (optional) field, then Invite….

Inviting creates an invitation, never an automatic member. The person only becomes a member of the schedule once they accept the invitation; they can also decline it. Until then, they see nothing of the schedule, and the schedule sees nothing of them — not their name, not their absences, not their workload in the risks. This holds even for an e-mail already known to PalmaPlan.

A pending invitation shows up in the same list ("e-mail · pending · role · expires on date") — by the address you typed, never by a name — with a Revoke button that cancels it: its link stops working right away.

What the invited person sees

In PalmaPlan, if they already have an account at the invited address: All schedules shows, above the list, an Invitations section — "Who invited them invites you as a contributor on “schedule name”." (or as an administrator, as a reader), Pending, the expiry date — with Accept and Decline. Accepting brings the schedule into Shared with me; declining removes the invitation, and the owner no longer sees it as pending.

Through the link in the mail, they land on an Invitation screen:

A declined or revoked invitation, opened again, says so: "This invitation has been revoked or declined."

What the role changes

Three roles, plus the owner — a special administrator, the only one who can move the schedule to the trash, purge it or transfer it. A schedule can have several administrators.

What you doAdministratorContributorReader
See the schedule, the kanban, the agenda, the history, the risks; export, printyesyesyes
Change rows, blocks, dependencies, columns, icons, the legendyesyesno
Create, assign, change, delete an actionyesyesno
Check off an action assigned to you (its status)yesyesyes, only their own
Open a comment thread, resolve ityesyesno
Reply in a thread — and edit or remove their own repliesyesyesyes
Their own absencesyesyesyes
The settings: work calendar, closures, information, printing, logo, "Set as default view"yesnono
Create a version, set the referenceyesyesno
Restore a version (it replaces everything)yesnono
Duplicate for yourself, save as a templateyesyesyes
Ask for an embedded view (show_schedule), which never does more than your roleyesyesyes, read-only
Invite, change a role, remove a member, revoke an invitationyesnono
Publish, adjust the embedded view, turn on exclusive editingyesnono
Leave the scheduleyes (not the owner)yesyes
Move to the trash, purge, transfer ownershipowner onlynono

A contributor opens Settings like everyone else, but doesn't change them: the fields are greyed out and the header says so ("Only an administrator changes these settings; you can see them without changing them.") — only the Show the legend box stays theirs. A reader sees Versions without creating or restoring any. What your role doesn't allow isn't offered on screen. The Actions menu offers every member Copy an embedded view (1 h): the address of a view of this schedule, the one an AI displays, which never does more than your role — read-only for a reader.

A reply in a thread belongs to its author alone: nobody else — not even an administrator — edits or removes it.

An agent (Claude, a named token) acts with the role of the person who connected it, never more; a read-only token writes nothing, whatever that role.

Changing a role: the menu next to the member's name, in MEMBERS; the change applies at once, and that person's open screen follows it live. Remove (on an existing member) or Revoke (on a pending invitation) takes access away right away.

Since 0.29.0, the former "editor" role is called contributor. A former editor became a contributor: they no longer adjust the schedule's settings or restore versions — the owner gives those gestures back by making them an administrator.

Leaving a schedule

A schedule shared with you — whatever your role — can be left from All schedules: its row's menu, Leave this schedule, then Leave to confirm (or Cancel). You lose access right away — a screen still open on it loses it live — and the schedule no longer sees your absences. It's the same departure as when an administrator removes you: the rows linked to you and the actions assigned to you stay in the schedule, which flags them as belonging to a removed member. To come back, you need a new invitation.

The owner can't leave their own schedule: they first transfer ownership to a member (below), and can then leave it as an administrator.

Transferring ownership

Still in Settings › Sharing, OWNERSHIP › Transfer ownership… opens a menu to pick an existing member, then Confirm the transfer (or Cancel). The text warns: "You will stay an administrator of the schedule; only the new owner will be able to move it to the trash or transfer it." — the transfer makes the chosen member the owner, and leaves you administrator on that particular schedule. Only the owner sees this section. An account can't close itself while it still owns schedules — see Account and data.

What happens when you get it wrong

What this page doesn't cover