Got a Docker Compose file? Your project goes live in seconds — one command on cdn.com.tr. See how Built your app with AI? From folder to live URL with one command — no git, no registry: cdnctl deploy. See how Code on GitHub? Every push auto-deploys to cdn.com.tr — connect your repo and ship. See how

CDN.com.tr Help

Add subusers and permissions

Invite or manage teammates with least-privilege access.

Organization, permissions, support

Add subusers and permissions

Invite or manage teammates with least-privilege access.

Panel path

  1. Management Panel
  2. Organization
  3. Subusers
  4. Roles / Permissions

Prerequisites

  • Subuser sees only accounts in parent-owner scope.
  • Role change should follow least privilege.
  • Subuser email and identity data are redacted.

Step-by-step guide

1

Create or select subuser

Delegation should avoid full billing/admin access when not required.

  • Open Subusers.
  • Create or select user.
  • Review role list.

Expected result: Subuser permissions are visible.

cdnctl equivalent 
# Subuser management is completed in the panel.
2

Verify route and account access

Subuser should see only screens in assigned role/account scope.

  • Assign role.
  • Log in as subuser for test.
  • Verify unauthorized route/API access is rejected.

Expected result: Unauthorized assets are inaccessible.

cdnctl equivalent 
cdnctl accounts list

Verification

  • Subuser PII is redacted.
  • Role-scoped access is preserved.
  • Unauthorized API returns 403/404.

Use cases

A developer should operate platform deployments without full billing access.

Quick workflow

  1. Open Organization / Authorization.
  2. Create or update subuser.
  3. Assign role.
  4. Verify accessible routes.

Checks

  • Role maps to intended route permissions.
  • Parent account ownership is preserved.
  • Revocation is available.

Related pages

Team roles: viewer, editor and owner

Give each colleague their own login and the smallest role that lets them do their job. The same role is enforced on the API, so a bearer token can never do more than the person it belongs to.

Activity history: who changed what

Every operational change on an account is recorded with the person behind it, the time, and the before and after values. Activity history answers "who purged that path" and "when did this record change" without asking support.