Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 35 ยท Getting Started

DigitalOcean Account, Projects, Teams and Billing Basics

Set up a DigitalOcean account safely: two-factor login, teams and roles, projects and environments, tags, resource URNs and billing alerts that prevent surprise invoices.

Before you create a single server, spend ten minutes on the account itself. A good setup makes everything later easier: you can separate production from experiments, give teammates only the access they need, and see exactly what each project costs. This lesson covers the account, teams, projects, tags and billing alerts.

Creating and protecting the account

You sign up with an email address and a payment method (a card or PayPal). Some new accounts receive promotional credit, but that depends on current offers, so do not plan around it. Right after signing up:

  1. Verify your email address.
  2. Turn on two-factor authentication (an authenticator app is better than SMS). Cloud accounts are a prime target because stolen access can be used to mine cryptocurrency on your bill.
  3. Add a billing email that a real person reads.
  4. Set a billing alert (explained below).

Never share your login. If several people need access, create a team instead.

Teams and roles

A team is a shared account. One person owns it and invites others by email. Members get a role that limits what they can do. The exact role names evolve, but the idea is stable:

Role idea Can do Typical person
Owner Everything, including billing and deleting the team Founder or tech lead
Member Create and manage resources Developer
Biller See and pay invoices, no access to resources Finance contact
Limited or read-only View only Auditor or contractor

Follow the least privilege rule: give each person the lowest role that lets them work. A developer rarely needs billing access, and an accountant never needs SSH access to servers.

Each team has its own resources, API tokens, SSH keys and invoices. Many people keep a personal team for learning and a company team for real products so that experiments never share a bill with production.

Projects: folders for resources

A project groups related resources (Droplets, databases, Spaces buckets, load balancers, domains, Kubernetes clusters and so on). It is an organizing tool and a billing lens, not a security boundary: projects do not isolate network traffic, and a firewall or VPC works across them.

A typical layout:

TEXT
shop-production     Droplets, database, Spaces bucket, load balancer
shop-staging        smaller copies of the above
shop-experiments    short-lived tests that you delete often

Every resource has a URN, a stable identifier such as do:droplet:314159 or do:dbaas:<uuid>. The API uses URNs to assign resources to projects, which matters when you automate:

Terminal
# Read-only example: assign a Droplet to a project with doctl
doctl projects list
doctl projects resources assign <project-id> --resource=do:droplet:314159

Each project also has a purpose (for example "Web Application") and an environment label (Development, Staging, Production). These labels help humans and reports; they do not change behavior.

Tags

A tag is a short label you attach to resources, for example env:production or role-web. Tags are powerful because other features can target them:

  • A Cloud Firewall can apply to every Droplet with the tag web.
  • A load balancer can send traffic to every Droplet with the tag web.
  • Scripts can list resources by tag.

New Droplets with the tag join automatically, so you rarely update rules by hand. Choose a consistent naming scheme early; tags are easy to add and annoying to clean up later.

Python Stand-in: group resources into projects by URN and tag

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The prices above are made-up round numbers to show the arithmetic; real prices depend on the plan you choose.

Billing: no surprises

DigitalOcean bills monthly in arrears: you use resources during a month and the invoice arrives at the start of the next one. Most resources are billed by the hour of existence, up to a monthly maximum. Three habits keep invoices predictable:

  • Billing alerts: set a threshold in the billing settings; you get an email when your usage passes it. Choose a number slightly above your expected bill.
  • Delete what you do not use: a powered-off Droplet is still billed because its resources stay reserved. Destroy it (after taking a snapshot if you may need it again).
  • Review the usage page at the end of each week during your first months.

Remember that some things cost money even when idle: unattached Reserved IPs, snapshots, volumes with no Droplet, and idle managed databases.

Python Stand-in: a billing alert checker

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Account hygiene checklist

  • Two-factor authentication on for every member.
  • One team per purpose; projects per environment.
  • Tags on everything that a firewall or load balancer should find.
  • Billing alert set, billing email monitored.
  • A short written note of who owns which project.

The next lessons build on this setup. You will create a Droplet, then learn to drive the account from a terminal with doctl.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a DigitalOcean project?

    Projects organize resources and make cost and ownership visible, but they do not isolate networks.
  2. 2. Why use tags such as 'web' on Droplets?

    Tag-based targeting means new resources are covered automatically.
  3. 3. A Droplet is powered off. Is it still billed?

    Power-off does not release the CPU, memory and disk. Destroy the Droplet (optionally after a snapshot) to stop charges.
  4. 4. Which role principle should guide team access?

    Least privilege limits the damage of mistakes and stolen credentials.

Summary

  • Protect the account with two-factor authentication and a monitored billing email.
  • Use teams and roles with least privilege; keep personal experiments separate from production.
  • Projects group resources, URNs identify them, and tags let firewalls and load balancers find them.
  • Set billing alerts and delete idle resources; powered-off Droplets still cost money.

Next: Your First Droplet Step by Step