WEBVTT

1
00:00:00.491 --> 00:00:05.064
Skylos Cloud · Chapter 13: Setting team policy
Decide once what fails a pull request. Every repository, every laptop and every pull request then gets the same answer.

2
00:00:05.064 --> 00:00:09.731
Step 1: Open Policy
Policy lives under Governance in the sidebar. Admins and owners can change it; everyone else can read it.

3
00:00:09.731 --> 00:00:16.518
Step 2: One page, five parts
Quality gate, Coding agents, Supply chain, Custom rules and History. One Save covers them all.

4
00:00:16.518 --> 00:00:22.466
Step 3: Start from the default
A new workspace blocks any new issue. Critical security issues always count, and exposed secrets are caught by that same rule.

5
00:00:22.466 --> 00:00:31.185
Step 4: Edit the conditions
Start from a preset (Recommended, Stricter on AI code or Strict) or set the rules yourself. Nothing is saved until you press Save.

6
00:00:31.185 --> 00:00:41.907
Step 5: Allow a few, block what matters
For older repositories: allow a handful of new medium and low issues, and keep critical and high at zero.

7
00:00:41.907 --> 00:00:46.451
Step 6: Always block exposed secrets
Tick this so secrets stay blocked even if someone loosens the limits later.

8
00:00:46.451 --> 00:00:56.584
Step 7: Say why
Skylos lists every change before you save. The reason is kept with this version in Policy history.

9
00:00:56.584 --> 00:01:06.361
Step 8: Preview before you save
Preview re-checks the latest scan of every repository against the new rules. Nothing is saved yet.

10
00:01:06.361 --> 00:01:12.645
Step 9: Save it
Each save becomes a new version. Repositories that inherit the policy use it on their next upload.

11
00:01:12.645 --> 00:01:18.446
Step 10: Stop repositories loosening it
Turn this on and a repository can make its own policy stricter, never looser.

12
00:01:18.446 --> 00:01:28.670
Step 11: Rules for code an AI agent wrote
Turn on agent rules, then choose Block, Warn or Off for each signal, such as weakened tests or a made-up package.

13
00:01:28.670 --> 00:01:43.443
Step 12: Supply chain
Block malware, hold brand-new package releases, and name your internal packages so look-alikes on public registries are blocked.

14
00:01:43.443 --> 00:01:49.396
Step 13: Your own rules
Custom rules add checks for patterns the built-in rules miss. They run in the CLI and on every pull request.

15
00:01:49.396 --> 00:01:57.134
Step 14: Every change is a version
Policy history shows who saved each version, when and why. Restoring an old one saves it again as a new version.

16
00:01:57.134 --> 00:02:18.103
Step 15: Check a branch from your laptop
skylos cloud --gate scans, uploads the findings and exits 1 when the team policy fails the branch.

17
00:02:18.103 --> 00:02:31.387
Step 16: See why in Skylos Cloud
The link opens the branch: the condition that failed, its limit and the count in this scan. A lead can still choose Merge anyway, with a recorded reason.

18
00:02:31.387 --> 00:02:38.414
Recap
Policy → Edit conditions · Reason for change, then Preview impact · Apply to every repository (stricter only) · Coding agents, Supply chain, Custom rules · History → Restore this version · skylos cloud --gate
