What verstag cannot do today

This page is a list of absences.

Deleting an account

Does not exist — no page, no button.

The route: a message to hello@verstag.io. The privacy notice names that route explicitly for access, deletion and portability.

Deleting a workspace

Does not exist. Renaming does: the owner changes name and address on the member page (Name and address).

The route: the same address as above.

Leaving a workspace

Does not exist. A member cannot even reach the member list.

The route: an owner or admin removes you. Only the membership disappears — account, profile and uploaded assets stay.

An account with no membership at all is a reachable state: signing in succeeds and ends on a card saying there is no workspace.

Exporting your own account data

Does not exist. The two exports that do exist belong to the workspace — the audit trails — and require a management role.

The route: the same address as above.

Managing sessions

Does not exist: no device list, no session list, no revoking individual sessions, no "sign out everywhere".

Signing out does act globally, though — on every device. Sign out and you are signed out everywhere.

There is no automatic sign-out on inactivity. The only rule about session lifetime verstag enforces itself is the renewal for enterprise sign-in — and that applies only in a workspace requiring it.

Sorting in the library

The library always shows the most recently added files first. No other order can be chosen.

Three tables do sort on a click of the column header:

• the batch overview
• a batch's results table
• the audit trail

The trail export always writes oldest-first, whatever sort the table currently uses.

What helps in the library instead: search by filename and the four facets under Finding something again.

Searching across all projects

Does not exist. The library’s search and filters apply within the open project; the overview of all projects has no search.

The route: if you have the file at hand, check it in the quick check. If it comes from your library, „In deiner Library“ (In your library) appears with a link to the asset — whichever project it sits in, provided you see that project.

Permissions per project

Does not exist. A restricted project decides who sees it, not what somebody may do in it. What members may do with projects — create, rename and delete, add and remove people and groups on a restricted project, set a project’s own export template — is decided by owners and admins under Settings → „Berechtigungen“ (Permissions), on every plan and for the whole workspace rather than per project. Groups carry no permissions either; they only give access. Only a whole project can be restricted, not a folder and not a single asset.

Likewise, the values under Usage and rights — „Nutzung durch Dritte“ (Third-party usage) and „Urheber und Rechte“ (Creator and rights) — apply to every manifest of the workspace, not per project.

The route: whatever not everyone should see goes into a restricted project of its own. Owners and admins can restrict a project, from the Growth plan up.

If you need one of these

hello@verstag.io. For anything concerning your data the address is in the privacy notice too.