# Quota and usage > Your tenant's CPU, memory and disk quota; what happens when the quota isn't enough, how to open a quota request, and your usage this month. The quota is the amount of CPU (vCPU), memory and disk your tenant can use at the same time. Servers, project environments, databases and kept disks all use the same quota. A server you've stopped also takes up room in the quota. ## Seeing your quota The **Kendi kotanız** (Your own quota) section on the **Sunucular** (Servers) page shows how much of the CPU, memory and disk is in use and what is using it: your servers, your projects, your kept disks and your databases. Other members' servers and projects you can't see also count against the tenant's quota; the section shows them separately too. ## If the quota isn't enough If the quota isn't enough for an action, the action isn't carried out: - **When creating a server**, the server isn't created, and a quota request for the missing amount is opened in your name automatically. Try again once the request is approved. - **When creating an environment, increasing an environment's size, setting up a project or adding a database**, a quota request button appears next to the error message; the request dialog opens already filled in with the missing amount. - **If what isn't enough is your personal quota or your team's share**, no quota request is opened; the error message says who can raise it. Your team manager or tenant admin raises your personal quota, and the tenant admin raises the team's share: [Team and personal quotas](#ekip-ve-kisi-kotasi). To free up room, you can delete servers you don't use, stop environments or delete [kept disks](/docs/en/sanal-sunucu#silmek-ve-saklanan-diskler). If persistent disk snapshots push you over your quota, you are warned and a red notice appears on the **Kota** tab; if the quota is not raised or space is not freed within 3 days, the oldest snapshots are deleted: [Environment size](/docs/en/ortamlar#ortam-boyu). ## Team and personal quotas The tenant admin can split the tenant's quota among teams and set an upper limit for each person. This is a setting turned on per tenant; while it's off, only the tenant's quota applies. The sections are on the **Kota** (Quota) tab of the **Ekip** (Team) page. - **Kota dağılımı** (Quota distribution, tenant admin): the «Ekip ve kişi kotalarını uygula» (Apply team and personal quotas) setting turns it on. Each team gets a share with «Pay ver» (Give a share); the shares together can't exceed the tenant's quota. The **Varsayılan kişi kotası** (Default personal quota) is the upper limit for everyone who hasn't been given a quota of their own; tenant admins have no upper limit. - Members of a team without a share can't create new resources. The tenant admin can allow it with the «Payı girilmemiş ekipler ekiplere ayrılmamış paydan kullanabilsin» (Teams without a share may use the undistributed share) setting. - **Kişi kotaları** (Personal quotas): for the tenant admin the list first shows the people with a quota of their own («Herkes» (Everyone) shows all members). The tenant admin changes anyone's quota, and a team manager only the quotas of their own team's members, with «Düzenle» (Edit) in the row's «⋯» menu, and returns it to the default with «Varsayılana döndür» (Return to default). A team manager can give at most the team's share. They can't change their own quota, the quotas of the team's other managers or those of tenant admins; the tenant admin does that. - A personal quota is an upper limit, not reserved resources: the personal quotas in a team can add up to more than the team's share. When a resource is created, the person's quota, the team's share and the tenant's quota are checked together. - The top of the tab shows the tenant's quota to the tenant admin, and to other members their own upper limit and what they use; your team's share is written below it. - If a quota is lowered, existing resources aren't touched; only creating new resources and increasing sizes stop. Decreasing sizes and deleting are always allowed. ## Opening a quota request **Open the request dialog** On the **Kota** (Quota) tab of the **Ekip** (Team) page, press the «+ Talep aç» (+ Open request) button. **Enter the amount and the reason** Fill in the CPU, memory and disk amounts to add to your current quota, and the «Gerekçe» (Reason) field. **Send it** Press the «Talebi gönder» (Send request) button. Opening a request doesn't reserve resources; the resources are added to your quota when the request is approved. A platform admin approves or rejects requests. The result reaches every member of the tenant with the **Kota talebiniz sonuçlandı** (Your quota request was decided) notification. The status of your requests appears on the same tab: «Beklemede» (Pending), «Onaylandı» (Approved), «Reddedildi» (Rejected) or «İptal» (Cancelled). To open a request you need the «Kiracı yöneticisi» (Tenant admin) or «Geliştirici» (Developer) role. ## Your usage this month The **Bu ayki kullanımınız** (Your usage this month) section on the **Kota** (Quota) tab shows the usage accumulated over the month: vCPU-hours, RAM GB-hours and Disk GB-hours. Every hour adds as much as the resources allocated at that moment; for example, a server with two CPUs adds two vCPU-hours in one hour. This isn't an invoice. - **Şu an ayrılmış** (Currently allocated): the CPU, memory and disk you're using right now. - **Günlere göre ayrıntı** (Breakdown by day): each day's usage. Disk hours include kept disks too. - Usage is updated once an hour. A day without a record doesn't mean you didn't use anything. If you see disk usage while you have no servers, it's because your kept disks and database disks are counted until they're deleted. ## Internet requests The same tab also has the **İnternet talepleri** (Internet requests) list: the internet access requests you've opened for your servers and environments. Details: [Internet access](/docs/en/internet-erisimi).