Documents

The Documents section lets you share files with your players — a program, the team’s rules, an administrative PDF — and see exactly who has opened them. You’ll find it in the team’s side menu, under Documents.

Each document is uploaded once, targeted at the whole team or a selection of players, then published. Your players find it in their app, in the Documents tab — see View my documents.

Upload a document

Open Documents in the team menu, then click New document.
Give it a Title (e.g. Team rules, Summer program).
Choose a Category: Program, Rules, Administrative or Other. It’s used to organise and filter your documents, on both the staff and player side.
Select the File. Accepted formats: PDF, image (JPEG, PNG, WebP, HEIC) or Office document (Word, Excel) — 20 MB maximum.
Set the Audience (see below).
Confirm: the document is created as a Draft. It is not yet visible to players until you publish it.

Choose the audience

On creation (and at any time afterwards via Edit document), choose who receives the document:

Whole team — all active players with portal access. This audience is live: a player who joins the team later will automatically see the document, with no action from you.
Selected players — tick the specific players concerned (useful for an individual program).

Publish and notify

A draft is published from its detail page:

Publish makes the document visible to the audience and sends a push notification and an email to each player concerned.
Tick Share without notifying before publishing to make the document available without a notification (useful for something they’ll read at their own pace).

STRIVN never notifies the same player twice for the same document. If you widen the audience later, only the newly added players are notified — never those who already received it, even if you switch between Whole team and Selected players.

Track who has read it

A document’s page shows a Read tracking panel: the X/Y seen counter and, player by player, Seen on {date} or Not seen. A read is recorded the first time the document is opened in the player’s app.

Two markers help you interpret the tracking:

Unreachable — the player has no notification channel (no push, no valid email). They weren’t notified; reach them another way.
Out of reach — active-roster players without portal access (invitation not completed). They’re listed separately and don’t count towards the X/Y seen, so the counter doesn’t imply full coverage.

Remind non-readers

On a published document, Remind non-readers re-sends a notification only to players who haven’t seen it yet. A reminder can be sent at most once per hour per document.

Edit, replace, archive, delete

From a document’s page:

Edit document — change the title, category or audience.
Replace the file — upload a new version. Read tracking is kept (the page shows File replaced on {date}) and players are not re-notified.
Archive — remove the document from the player portal without deleting it; it moves under Archived and stays visible to staff. Unarchive puts it back online, with no new notification.
Delete — permanently erase the file and its read tracking. Irreversible.

From the AI assistant

You can also ask the AI assistant “which documents have I shared and who has read them?”: it lists your documents with their tracking. It can also propose to publish, adjust the audience, archive or remind an existing document — you confirm before the action runs. The assistant cannot upload a file: uploading stays a manual action.