Reviewing and running it

Reviewing photos

Photos is the queue. Before you approve anything you have to say where approved photos go — that is what Approving to in the toolbar is. It stays put while you are signed in, so you choose once and work through the queue.

The review queue with a destination chosen, named in the toolbar above the photos. — Choose the destination once; every approval after it goes there.

Photos and events keep separate destinations on purpose — a photo board and a calendar board are a normal split.

From the keyboard

Arrow keys move through the queue.
Space selects, so you can act on several at once.
Enter opens one full size.
a approves, r turns one down.

Turning something down

Rejected photos are not deleted. They sit in Rejected for a month by default and can be put back at any point — putting one back asks where it should go, because it is being published for the first time.

You can type a reason. It is worth doing: the person sees it when they open Activity, and it is the difference between "no" and a reason.

Turning a photo down does not email the person who sent it — not if they have an account. They see it in Activity when they next look.

The one exception is somebody who sent from a QR page that confirmed their email address. They get an email, and only if you typed a reason: a bare "no" by email is worse than silence.

Events

Events are reviewed the same way, and you can fix the details before approving — a title, a time, a place, a category. Past events drop off the screens on their own.

Boards

A board is one stream of content. Every screen is pointed at a board, and approving a photo is choosing which boards it goes to. One board is enough until two locations need different things.

A photo already approved can be sent to different boards later, from Approved photos. That is a separate action from approving it again, and deliberately so — re-approving would re-send the "your photo is up" notice.

People

There are three roles:

Member — sends photos and events.
Moderator — also reviews the queue.
Admin — also changes boards, screens, people and settings.

Everyone can see every Setup screen; the buttons that change things are the ones limited to admins. Hiding a screen would tell a moderator it does not exist rather than that they may not change it.

Adding someone

Publish a QR page set to members you approve and send people to it. They register, you get them in the queue, and approving them emails them a link back to the page.

Blocking someone

Blocklist takes an email address or a phone number, and blocks the person rather than the string: the account behind it is closed and signed out at the same time. If the address turns out to belong to more than one account, it tells you which, and does nothing until you say to go ahead.

An organization can never lock itself out — nothing that would remove the last active admin is allowed.

QR upload pages

The Upload pages screen, listing the QR pages an organization has published. — Upload pages. Each one has its own link, its own poster and its own rule.

Each page answers "who can send here?" in one of three ways:

Anyone — a name, and optionally an email or phone. Good for an event full of visitors. The address is whatever was typed, so the queue marks it as unconfirmed.
Confirmed email — the page emails a six-digit code before it accepts anything. Slower, and the only kind where you know who sent it.
Members you approve — people register through the page and an admin lets them in.

Print the QR code from the page’s own screen. You can pause a page after an event without deleting it, and a paused page simply stops working.

Settings

Your organization’s logo, the name the screens print, how long each photo stays up, how far ahead the calendar looks, how long rejected photos are kept, and whether moderators and admins get a daily email when something is waiting.

Every row says where its value came from. Reset to default is not the same as typing today’s default in: it goes back to following the default, so a later change reaches you.