Work and teams

Set up team policies and the audit log

Apply admin-signed policies that devices enforce locally: switch features off, limit files, protect the clipboard, allow LAN only.

Available in preview 1 min read Updated Applies to
  • Windows
  • Android
  • Linux

Organisations can manage devices without accounts or a cloud console. An administrator signs a policy with a private admin key; each device checks the signature and enforces the policy itself.

Steps

  1. Create an admin key (administrator)

    On the administrator’s PC run pdb team init. Keep the key file private.

  2. Write and sign a policy

    Describe the rules in a JSON file, then sign it with pdb team sign policy.json --org "Your company". This creates team-policy.json.

  3. Enroll each device

    On each PC open Settings › Security & organisation › Organisation › Team enrollment. Enter the organisation name and the Admin key, then click Enroll.

  4. Apply the policy

    Click Apply policy file… and choose team-policy.json, or run pdb team apply team-policy.json. pdb policy shows what is in force.

What a policy can do

  • Switch individual features off.
  • Block file types or set a maximum file size.
  • Keep resident registration and card numbers out of the clipboard.
  • Allow the local network only, with no internet connections.
  • Require the audit log.

Clipboard rules

In clipboard_block use kr_rrn (resident registration numbers), card (card numbers; only valid card numbers are blocked), kr_phone or email; to block other text write re: followed by a regular expression. Look-alike dashes, other digit forms, dots or tabs as separators and invisible characters are handled. The same rules cover text and links sent to My Drop. Unknown rule names are refused when you sign the policy.

Audit log

Audit log records what each device did in a chain of hashes, so later changes are detectable. Verify integrity (or pdb audit --verify) checks the chain. There are no accounts, SSO or cloud console by design.