Skip to main content

Policies

Administration → Policies. Rules that apply to everyone in the organization. Only owners and admins can change them.

When this is on, members can only paste or type links to Sekee itself. Anything else is refused as it is pasted, and again when it is saved.

It exists for organizations where a test case, bug or comment must not become a route to somewhere unreviewed.

While it is on​

The same points are behind the (i) beside the switch, so they can be read before turning it on.

  • Linking a Jira issue keeps working. Your connected Jira's own domain counts as inside, and so do the links Sekee writes on its issues.
  • Bare domains count too, so example.com is refused as well as https://example.com. Email addresses and filenames are not.
  • Links Sekee writes itself — a /tc reference to a test case — keep working. So do the screenshots and files you upload, wherever Sekee stores them.
  • Existing content is left alone. The policy applies to what gets saved from now on, not retroactively.

How it is enforced​

Twice: the browser refuses the paste so you find out immediately, and the server refuses the save so a client that skipped the first check does not get through.

The two share one source of truth — the allowed host list travels to the browser with your session — so the field cannot reject what the server would have accepted, or the reverse.

:::note What the screen shows you The page names your connected Jira, because that is the exception worth knowing about. It does not list Sekee's own storage hosts, which are always allowed and are not a fact about your organization. :::

Turning it on​

Flip the switch. There is no migration and nothing is rewritten — existing content keeps whatever links it has.

Turning it off is equally immediate, and previously refused content is not retrospectively accepted, because it was never saved in the first place.

Require two-factor authentication​

Everyone in the organization needs a code from an authenticator app as well as a password. See Two-factor authentication for what that looks like from a member's side.

The deadline​

Turning it on sets a date, fourteen days out by default. You can move it whenever you like — a team at a conference is the usual reason — but never to less than 24 hours away, so nobody can lock the whole organization out with a mis-set date picker.

  • Before it, anyone who has not set two-factor up sees a banner on every screen naming the exact date. They keep working.
  • On it, they are signed out. Signing in again takes them to the setup screen and completes the sign-in once they are enrolled.

The Deadline panel also counts how many people have not set it up yet.

Things worth knowing before you turn it on​

  • You need two-factor on your own account first. Sekee refuses otherwise. Without it the deadline eventually catches you too, and the person who could reset it would be the person who needs it reset.
  • Viewers are not affected. A viewer is somebody outside the company with read-only access that expires on its own; requiring an authenticator app to open one report would make sharing a report a support conversation.
  • Nobody covered by the policy can turn their own two-factor off while it stands. Switch the policy off first.
  • Switching it off clears the deadline rather than leaving a stale date behind. A past date under a re-enabled policy would mean everyone is locked out the same second.

Changes to this policy are written to the activity log.