Organizations acme-corp Manage
Manage acme-corp
Members, repository defaults, webhooks, and danger zone.
General
How acme-corp appears across Cloudzilla.
Using 1.2 GB of 10 GB storage across 14 repositories.
PNG, JPEG, GIF or WebP, max 2 MB.
Members
47 people. Owners create repositories and manage the org; members need a collaborator role on each repository they work on.
Teams
Group members and grant batch access to repositories.
Teams aren't wired up yet.
Group your members into teams in a future release; the surface lives here.
Repository defaults
Applied to new repositories created under acme-corp.
Webhooks
Receive HTTP POSTs for org-wide events. Signed with HMAC-SHA256.
Org-level webhooks aren't wired up yet.
Per-repo webhooks already work — find them in each repository's settings.
Audit log
Recent admin actions on acme-corp — profile edits and repository-default changes.
- org.profile.update @mkappworks updated profile on acme-corp
- repo.create @daisy created acme-corp/runner
- org.defaults.update @mkappworks updated repository defaults on acme-corp
- repo.transfer @mkappworks transferred legacy-site
- repo.delete @daisy deleted scratch-pad
Danger zone
Irreversible operations that affect everyone in the org.
-
Transfer ownership
Hand over acme-corp to another user. You'll be downgraded to Member.
-
Delete organization
acme-corp still has 14 repositories. Delete or transfer them first — deleting the org cascades through every repo, issue, PR, and comment.