Organization settings

Your organization is the thing that owns your festivals: the people who run them, its name and support address, the account it is paid into, and the record of who was let in. This is the screen where all of that lives.

It has six tabs. Most of the work happens on the first one, People — a list of everybody in the organization, with a menu on every row and a panel behind every name.

Finding the screen

Organization settings is the last row of the top block of the left navigation, under Library. Its address is:

/org/<organization>/settings

While your organization has no mailing address, the row carries an amber 1 and opens straight on the Organization profile tab instead of People. Both go once an address is saved — see Organization profile.

Each tab has its own address, so you can bookmark one or send it to a colleague:

An address with no tab, or with a tab name FilmScorecard does not recognise, opens People rather than an error.

Organization settings in your account menu, behind your name in the top-right corner, still does nothing. That row is greyed out. Use the navigation row.

Who can open it

Only an owner or an org admin, and only while their access is active. Everybody else gets an ordinary "page not found":

• A Member of your organization — including someone who runs a festival for you every day — cannot open it.
• Someone whose organization role is Finance cannot open it either. That role reaches nothing in this release — including the Payments tab.
• Somebody whose access you have suspended cannot open it, whatever their role.
• Anyone outside your organization sees exactly the same "page not found" as a mistyped address. Your organization's existence is never revealed.
• A logged-out visitor is sent to the log-in screen first.

That single answer is deliberate: a stranger guessing addresses learns nothing from it, and neither does a member who was not meant to be here.

Every change on this screen is checked again on the server when you commit it, so a refusal is a refusal however the change was attempted. The Export CSV download on the Audit log tab is guarded the same way, and so are the two links out to Stripe on the Payments tab.

The header and the tabs

Above the tabs: your organization's name in small capitals, the title Organization settings, and one line that describes the whole model:

People are invited to the organization, then given a role on each festival they work on. Owners and org admins reach every festival without an invitation.

The tab row carries up to three counts:

• People — everybody in the organization, suspended people included.
• Pending invitations — invitations nobody has accepted yet. It turns amber as soon as there is one.
• Organization profile — an amber 1 while your organization has no mailing address. It goes once one is saved.

No other tab ever carries a count or turns amber — including Payments, whatever state your payout account is in.

There is no Security tab. Single sign-on, allowed domains and two-factor rules do not exist, and nothing is drawn greyed-out for them — they are simply not there.

The three organization roles

An organization role decides org-wide reach. It is chosen when somebody is invited and can be changed afterwards.

Owner and Org admin are drawn with an indigo pill, Member with a quiet one — the colour marks reach, not seniority.

Two things to know about the list:

• Org admin is the role other guides call a staff member. It is the same role, renamed; the top bar now reads "Org admin" under the name of anyone who holds it.
• A fourth role, Finance, exists in the database and is hidden everywhere in this release — it is not offered when you invite somebody, not offered in any role menu, and not shown on the Roles and permissions tab. It reaches nothing today, the Payments tab included. If somebody in your organization already holds it, their row shows the pill honestly and you can change it like any other.

The Owner card mentions billing. There is no billing screen — no plan, no seats, no invoices. What the owner does have that nobody else does is the payout account on the Payments tab.

An organization always keeps one owner

The last active owner cannot be demoted, suspended or removed. Those items in their row menu are drawn as plain grey text with the reason underneath:

Transfer ownership first, an organization keeps one owner.

To hand the organization over, make somebody else an owner first — only an owner can do that — and then change your own role. An organization may have several owners at once.

Somebody who already owns another organization can be made an owner of yours. One person may own several organizations: you can promote them from their row menu or their access panel, or invite them as an owner — see Your organization invitation. What one person cannot do is create a second organization themselves: setting one up from scratch is still one per person — see Setting up your festival. Each organization they own keeps its own people, settings and payout account; see Working in two organizations.

Ownership is also who may manage payouts. Handing the organization over hands over the Stripe payout account with it — see Connecting payouts.

What an org admin cannot do

An org admin manages everybody except an owner. On an owner's row, Change org role, Suspend access and Remove from organization are greyed with the note "Only an owner can manage another owner." An org admin also cannot make anybody an owner: the Owner option is absent from every role menu they see.

Two items are not greyed on an owner's row and behave differently:

• Edit festival access opens the panel as usual, and the refusal arrives only when you press Save access.
• Send password reset works — an org admin can send an owner a password reset email.

An org admin also cannot act on the Payments tab's payout account: they read it and nothing more. They can set the judge payment terms on the same tab, exactly as an owner can — see Judge payment terms. They are emailed whenever an owner disconnects the payout account or connects a new one — see Who is emailed when the account changes.

The People list

Reading a row

• Person — the name over the email address in monospace. The name is a button: it opens that person's festival access panel. Where somebody has no name recorded, the address is used as the name too.
• Org role — one of the three pills above.
• Status — Active (green) or Suspended (amber). A suspended row is drawn quieter than the rest.
• Festival access — a number over a short qualifier:
  • "All 8" over "by org role" for an owner or an org admin, because that is what those roles reach.
  • the count of distinct festivals the person has been granted, over "festival"/"festivals" — or over "2 customized" when some of those grants have had their capabilities changed.
• Last active — a date, or "—". Read What "Last active" measures before relying on it.
• The three-dot menu at the end of the row — see The row menu.

Hovering a row turns its row number into a checkbox. On a narrow window the row restacks into labelled lines and the column headings hide themselves; on a phone the checkboxes are simply always there.

What "Last active" measures

It is the last time that person opened this Organization settings screen — nothing else. No other screen in FilmScorecard updates it, and the write is skipped if their last one was under an hour ago.

The consequences are worth stating plainly:

• Every Member shows "—", permanently, because a member cannot open this screen at all.
• An owner or org admin who works in Submissions all week but never opens Organization settings shows the date they last came here.

Do not read a dash as "this person has never signed in". It means FilmScorecard has nothing to report.

Searching, filtering and sorting

The toolbar above the table:

• Search people matches name and email address, ignoring capitalisation, and filters as you type. There is no Search button — the whole list is already in front of you. A ✕ appears inside the box once there is text; Escape clears it too.
• Org role — a multi-select with the three visible roles and a count beside each, plus Select all and Clear.
• Status — Active or Suspended, one at a time. Choosing the one already set clears it.
• Festival — a multi-select of your organization's festivals. Its counts are of the people who reach each festival, so every owner and org admin is counted under every festival even though they hold no grant on any.
• Clear filters appears as soon as anything is set.

Somebody matches if they hold any of the roles ticked, and must satisfy all three filters together. Every count is measured across the whole list and never cross-filtered, so ticking a box never changes the numbers beside the others.

All five column headings are sort buttons. Click once to sort, click again to reverse; the active heading carries a caret. The list arrives sorted by Person, A to Z, and the name breaks every tie. Org role sorts by seniority rather than alphabetically. Sorting by Last active puts people with no date first going up and last coming down.

Changing the search, any filter or the sort clears any rows you had ticked. That is deliberate: a bulk action against rows nobody can see is the one way this screen could act on people you did not mean.

The footer line

One line under the table:

14 of 14 people, no filters, sorted by person

The middle clause reads "filtered" as soon as anything is narrowing the list.

When the table is empty

Two different states, because they need two different answers:

• Nobody else yet — "Nobody else is in this organization yet", with "Invite the people who run your festivals, then give each of them a role on the festivals they work on." and an Invite people button.
• Nothing matches your filters — "No people match these filters", one line naming what is set ("Filtering by search "ada" · Member · 2 festivals."), and Clear filters.

The row menu

The three-dot menu opens headed by the person's name and email, so you can be sure whose row you are on.

Nothing here writes on click except Send password reset, which has nothing to undo. It reports at the bottom of the screen: "Password reset sent to [email protected]."

Items you may not use are drawn as grey text with the reason underneath rather than removed, so their absence is never mistaken for something missing. That happens in two cases: the last owner, and an owner's row seen by an org admin.

Changing somebody's organization role

Change org role opens a dialog headed with their name and "currently Member", a role menu, and one line:

Owners and org admins reach every festival without a grant. Members reach only the festivals they are granted.

Changing somebody from Member to Org admin does not delete their per-festival grants — the org role simply overrides them while it lasts. Change them back to Member and the grants they had apply again exactly as before.

Making somebody an owner works whether or not they own another organization. Only an owner sees Owner in this menu.

Suspending, restoring and removing

Suspend access

The confirmation reads:

Suspend access? [email protected] They lose all access to this organization immediately.

What suspending actually does:

• They keep every festival grant they had. Nothing is deleted, which is why restoring needs no re-granting.
• They cannot reach anything belonging to this organization — not a festival, not a season, not this screen.
• It takes effect on their next request, not instantly. Somebody with the app already open is not signed out and does not see anything change until they load or reload a page. From that moment there is nothing there.
• Their row stays on the list, drawn quieter, with an amber Suspended pill.

You cannot suspend yourself. The menu offers it and the confirmation refuses: "You cannot suspend your own access." In the access panel the Suspend button is greyed on your own row instead.

A suspended owner cannot manage payouts either, for the same reason: every payout action re-asks whether you are an active owner at the moment you press it.

Restore access

Restore access? Their festival access was kept while they were suspended, so it resumes exactly as it was.

Restoring is one change and nothing else: their grants, their org role and their festival roles are all as they were.

Remove from organization

Remove from organization? Ada Reyes · [email protected] · 3 festivals Their membership and every festival grant it carries are deleted. Invite them again to bring them back.

Removing is permanent. The row disappears, every grant goes with it, and the only way back is a fresh invitation. You cannot remove yourself.

Working on several people at once

Tick any row and a bar floats at the bottom of the screen: "6 selected", with Clear selection, Grant festival access, Change org role and Suspend.

All three open a confirmation first, and each confirmation states how many of the selected rows it will actually touch — the counts are the point.

Two limits worth knowing:

• Owner is not offered in the bulk role menu, and the action refuses it ("Owner is set one person at a time."). The dialog says so too: "Owners are set one person at a time and are skipped here." Ownership is the one role that manages owners, payouts and the organization itself, so it is given one person at a time — from the row menu, the access panel or an owner invitation — and never as part of a multi-select.
• A bulk change that would leave the organization with no active owner is refused outright, before anything is written: "An organization keeps one owner. Transfer ownership first."

Afterwards a line at the bottom of the screen says what happened: "4 people granted access, 2 skipped."

There is no bulk remove and no bulk invite.

Organization profile

Four fields in a row, a one-line Mailing address field under them, and a Save profile button. Nothing here saves by itself.

All but the name may be left blank.

The line under Mailing address says why it is asked for. With an address in the field it reads "Printed at the foot of emails that sell something, like promo codes and scorecard unlock offers. The law requires a postal address on those, and a PO box works." With the field empty it turns amber and reads "Promo code and scorecard offer emails can't be sent until you add one: the law requires a postal address on emails that sell something. A PO box works." While no address is saved, the Organization profile tab and the Organization settings row in the left navigation each carry an amber 1, and owners and org admins see "Add your organization's mailing address" under Needs attention on the season dashboard, with Open Organization profile. On the organization Overview, they also see Mailing address missing at the top of Needs attention, with Add in Settings →. All of them go once an address is saved.

Renaming the organization does not change its web address. The line under the field says so: every link anybody has already been given keeps working, and /org/<organization> stays exactly as it is.

Beside the button, once you have saved at least once, a quiet receipt: "Saved just now" immediately after a save, and "Last saved Aug 11, 2026, 10:04 AM by Ada Reyes" on a later visit. It is absent until the first save rather than showing the date the organization was created.

What these fields actually reach today:

• The name is what every screen in FilmScorecard shows for your organization, and it is the name in the invitation email people get when you invite them. It is also the sender's name on a promo code you email: "Your organization via FilmScorecard".
• The support email becomes the reply-to on the email FilmScorecard sends on your behalf — organization invitations, judge invitations and promo codes you email from Promo codes — so a confused invitee or filmmaker replies to you rather than to a no-reply address. Unset, it falls back to FilmScorecard's own sending address.
• The support email also receives filmmakers' messages for any season without its own Contact email: a filmmaker's Contact the festival goes to the season's address first, then this one. With neither set, filmmakers see no way to contact you. See Messages from filmmakers.
• The time zone is read in two places. On Promo codes, a code's start and end dates — and so whether checkout accepts it on a given day — run midnight to midnight on this zone's calendar, or on UTC while it is Not set. And the email every owner and org admin gets when the payout account is disconnected or connected prints its time in this zone, or in UTC while it is Not set — see Who is emailed when the account changes. Nothing else reads it yet.
• The mailing address is printed at the foot of every promo code email, as an offer email must carry its sender's postal address — and until it is set, Email this code refuses to send. It is printed under the name, as you typed it. See Emailing a code.
• It is also in the footer of the emails filmmakers get about their submission — the results email and the email that sends them to their submission page — on one line, after "Sent by FilmScorecard for your festival". With no address set, that line simply ends at the festival's name; those emails still send.
• Legal entity is read in one place: the foot of a promo code email, where it is printed above the mailing address in place of the organization's name. Left blank, the organization's name is printed instead. The line under the field describes where it is heading, not where it is. In particular, the legal entity here is not what Stripe verifies — the payout account asks for its own details and keeps them on Stripe's side.

Profile saves are not recorded in the Audit log. That tab keeps access changes only.

Picking a time zone

The Time zone field used to be a box you typed a name into, refused on save if the spelling was wrong. It is now a list with a search box, so there is nothing to spell:

1. Click the field. The list opens under it with the search box ready to type in; Not set is the first row, then the US zones starting with Eastern Time, then UTC, then the rest of the world from west to east.
2. Type any part of a zone's name or one of its cities. Case does not matter, so pacific, los angeles and berlin all find their zone.
3. Choose a row. The list closes and the field shows it. Choose Not set to clear the field — blank is a real answer here, and it saves as one.
4. Choose Save profile, as for any other field.

If nothing matches, the list reads No match for "…". with a Clear search link; it is never simply empty. Escape clears what you typed, or closes the list once the box is empty; clicking anywhere else closes it too. Opening the list again always starts from the full list.

A saved zone the list leaves out stays in it. A zone typed in before the list existed — US/Pacific, say — or a less common one such as America/Detroit is its own row, just under Not set, under its everyday name and then its stored one: "Pacific Time, US/Pacific". Saving without touching it is accepted as it always was, and picking another row replaces it.

Payments

Two cards: your organization's payout account, and under it your judge payment terms.

The payout account

The first card is the Stripe account your festivals are paid into. One account covers the whole organization — every festival, every season.

It shows a status pill in one of five states, a date, the Stripe account reference and the platform fee, and offers the owner one main button — with a quieter Disconnect beside it once an account exists, for switching to a different Stripe account. Only the organization owner can act on it; an org admin reads the same card with no buttons and the line "Only the organization owner can manage payouts."

A disconnect, and every new connection, emails every active owner and org admin, so nobody can repoint the organization's scorecard money without the others hearing of it.

Bank details, balances, payout schedules and payout history are never on this tab — they live in Stripe's own dashboard, which the card links to once payouts are running.

What is paid into it is scorecard sales — filmmakers unlocking the scorecards your judges wrote, less the platform fee on the card. That side of it is Selling scorecard access; judge pay does not go through this account, or through Stripe at all.

Each organization has its own payout account, including two organizations the same person owns. Setting up the second one on Stripe can reuse the details you gave for the first. See Working in two organizations.

The whole of it — the five states, setting the account up, disconnecting it, the platform fee line, the Setup Home step and the dashboard banner — is Connecting payouts.

Judge payment terms

The second card, headed Judge payment terms, says when your organization pays a judge's invoice. Its current setting is printed under the heading — "Paid 30 days after invoice", or Not set. Owners and org admins can change it.

1. Pick one:
   • Not set
   • 7 days after invoice, 15 days after invoice or 30 days after invoice
   • The 1st of the month or The 15th of the month
   • Custom: days after invoice — type a number of days, 1 to 120
   • Custom: day of the month — type a day, 1 to 31
2. Press Save terms. "Payment terms saved." appears at the bottom of the screen.

One set of terms covers every festival and every judge in the organization. What they reach:

• Every invoice a judge sends you carries them, with the due date they give — see Judge invoices. "Day of the month" means the first such day after the invoice date; a month too short for it uses its last day.
• Judges see one line beside every rate you show them — "Paid 30 days after invoice", or "Paid on the 15th of the month" — on invitations and their email, your open calls and the replies you send to applications, your public page's Judging tab, and their pay statements and Earnings screen.
• Not set puts no line anywhere, and invoices read "No payment terms set" with no due date.

Changing the terms never changes an invoice already sent. It changes the next invoice, and every terms line from now on.

Nothing done on the Payments tab is recorded in the Audit log either — a disconnect and a change of terms included. That tab is access changes and nothing else.

Audit log

Headed Access changes, with "Every grant, revoke and role change, kept for 24 months." Newest first, 50 at a time, with Load more underneath.

Every sentence the log can write:

Empty, it says so: "No access changes yet" / "Role changes, grants and invitations appear here as they happen."

Export CSV

The button top-right downloads the whole log — every event, not just the ones on screen — as a file named after your organization and today's date, with the columns When, Actor, Change, Scope. Its When column holds the full raw timestamp rather than the tidied one on screen.

A name that begins with =, +, - or @ — a person's or a festival's — is written with an apostrophe in front of it, so a spreadsheet shows it as text instead of running it as a formula.

An organization with no events still downloads a valid file with the four column names in it, rather than an empty one that looks broken.

Two things about the log

• Nothing can be edited or deleted from it, by anybody, including you.
• Load more tops out. It adds 50 rows a time and stops growing at 2,000 events on screen. Beyond that, use Export CSV — the download has no limit.

No money event is in this log. A scorecard sale, a comp and a refund are none of them access changes, and none of them appear here — the season's Revenue card and its CSV are where sales are recorded. Nor is a promo code email: its sends are listed on that code's panel on Promo codes.

If something is refused

Nothing on this screen is optimistic. A change is written when you commit it and the screen re-reads the server's answer afterwards; if it is refused, nothing was saved and the screen never moved. Dialogs and the access panel stay open with the message inside them; everything else reports at the bottom of the screen.

What this screen does not do yet

• Billing. No plan, no seats, and nothing your organization is ever charged for. The Payments tab is the payout account — money coming in — and the terms your judges are paid on, and the hidden Finance role cannot reach either.
• Security settings — single sign-on, allowed domains, two-factor rules. None of it exists.
• Per-capability permissions are mostly recorded, not enforced. The tick boxes on a grant are stored and shown, and the first one with teeth is "Approve scorecards and resolve flags", which decides who can act on the Review Queue. The second is "View revenue and payouts". Beyond those, the only thing the product enforces is the coarse split: a Viewer cannot change anything. See Festival access.
• Nothing ages out of the audit log. "Kept for 24 months" describes the intent; nothing is deleted today.
• Last active only counts visits to this screen. See What "Last active" measures.
• Legal entity, the mailing address and the time zone reach very little. The legal entity is printed only on the promo code emails you send, and the mailing address on those and in the footer of filmmakers' results and submission-page emails; the time zone is only the calendar Promo codes run on and the time printed on a payout account email.
• There is no way to cancel an invitation once it is sent — see Inviting people.
• No sales figures are on this screen. What your festivals have earned is per season, on each season's Revenue card — see Selling scorecard access.
• No list of who has unsubscribed from your promo emails. See Promo codes.

Related guides

• Inviting people — the invitation dialog, the Pending invitations tab, resending, and what the email says.
• Festival access — the panel behind a person's name, the four festival roles, and the capability matrix on the Roles and permissions tab.
• Connecting payouts — the Payments tab: the five states of your payout account, setting it up on Stripe, disconnecting it, the platform fee line, and who may act on it.
• Selling scorecard access — what the payout account is for: what a scorecard unlock costs, what your organization earns, and where the figures appear.
• Judge invoices — the invoices your judges send, which carry the payment terms set on the Payments tab.
• Promo codes — your organization's own discount codes, whose dates run on the time zone set on the Organization profile tab, and which you can email from your organization's name and mailing address.
• Working in two organizations — moving between organizations you belong to, including two you own.