Settings: your profile, your workspace, and who is in it

Profile: how you appear

Your photo, your first name, and your last name. The first name is required because it is how the app greets you; the last name is optional. Your name shows in greetings, the account block, and on your work.

The photo has its own article, “Profile pictures.” The short version: PNG, JPEG, or WebP up to 2 MB, resized to a small square, location data removed, and the circle beside the button is exactly what teammates see.

Your email is shown but not editable. It comes from how you sign in, and changing it here is not supported yet. There is no password field on this page either: to change your password, use the reset link from the sign-in page, which has its own article.

Workspace: the name and the slug

The workspace name is what everyone in it sees at the top of their screens. Admins can rename it here, and renaming changes the display name everywhere at once. Everyone else sees the name with a one-line note saying to ask an admin.

Under it is the workspace slug, the short identifier set when the workspace was created. It never changes, and renaming does not touch it.

Organization brand: defaults for new events

This card holds the guest-agenda branding a new event starts with: a primary colour and an accent colour as six-digit hex values, a logo by URL, and a default template. Fill in any or none. An empty field means no default, and a new event starts on the Classic template with nothing pre-filled until someone sets otherwise.

The honest sentence the card keeps repeating, because it is the one people get wrong: these are defaults for events you create from now on. Events that already exist keep what they have, and each event’s own Guest agenda controls always win over these. Changing the defaults never restyles a show you have already built.

The logo has to be an https link on a host we allow. If a link cannot be used, saving tells you so rather than quietly dropping it. Admins edit this card; everyone else sees the current defaults read-only.

Team: who is in this workspace

What this card shows depends on who is looking, and the differences are deliberate.

An admin gets the invite form, the list of everyone in the workspace with a seat and an access control on each row, the pending invites with how many days each has left and a Revoke button, and a count of seats in use. The count is informational: nothing is billed or limited by it today. The seats themselves, what each one can do, and what an invite link does are all in “Seats and access,” which is the article to read before you send anyone a link.

An editor or a viewer with access to the whole workspace sees the same list read-only, with a note to ask an admin for changes.

Someone whose access is limited to specific events does not see the list at all, not even the headcount. They were brought in for one show, and the client’s staff directory is not part of that. Their card says who manages access and offers the one control they are most likely to need, which is the next one.

Leaving a workspace

“Your access,” at the foot of the Team card, is there for every seat. “Leave this workspace” asks once more, names the workspace, and then ends your access to every event, run of show, and export in it. Nothing you built is deleted, your Planet Events account stays, and an admin can invite you back.

It refuses in one case: you are the only admin, because a workspace cannot be left without one. If there are other people, make one of them an admin first. If you are the only person in the workspace, there is nobody to hand it to, and the card says the true thing: deleting a workspace is not something the product can do on its own yet, so write to us and we will sort it out by hand.

What is not here yet

No billing or plan, because there is nothing to pay for yet. No email or password change on this page. No notification settings, because there is nothing to configure: the product sends no notification mail. No delete-account and no delete-workspace; both are a message to us for now. Anything that belongs to a single event, such as its dates, its brand colours, or its guest agenda, lives on the event rather than here.

What is coming, and when, stays planetevents.io/roadmap’s question.