In ownCloud Infinite Scale (oCIS), “user quota” usually means the quota assigned to that user’s personal space. A space is a storage area with its own access rules and quota; project spaces can have separate quotas. That distinction matters: raising a personal-space quota does not automatically change a project space, and a server-wide maximum is not the same as setting one person’s allowance.
This guide shows the documented ownCloud Web method for an individual account, explains how to set a quota for newly provisioned users by role, and points out the configuration limits that are easy to confuse. The exact controls available depend on your oCIS and Web versions and on how user identities are managed. The linked ownCloud Web admin guide documents user editing and quota assignment; check the documentation that matches your deployed release before making changes.
First identify the space whose limit needs to change. If the user is filling their personal Files area, change the quota for that user’s personal space. If the problem is a team or project space, change that space’s quota instead. ownCloud describes spaces as independently quota-bearing storage areas, including personal and project spaces. See the Infinite Scale architecture and spaces overview.
Next, confirm who manages the user account. A user created in the built-in identity provider may be editable in the Web user-management screen. If your deployment uses an external identity provider or synchronized directory, the identity provider, provisioning policy, or a role mapping may control some account properties. The current documentation does not establish one universal administration path for every identity-provider setup, so verify the source of authority for your account before editing it.
For a user you manage in ownCloud Web, the documented workflow is to open User management, select Users, edit the account, and assign a quota for that person’s personal space. The labels and available values may differ by release.
ownCloud’s Web for Admins documentation says that existing user details can be edited from the Users overview and that a user needs both a role and a quota assigned for their personal space. The guide includes selectable quota values, but does not promise that every deployment offers the same presets or a custom-value field. If the value you need is not offered, check the documentation for your exact oCIS/Web version and deployment configuration rather than assuming a setting from ownCloud Server applies.
A quota controls how much data can be stored in the corresponding space. It is not a reservation of that many bytes on the disk, and it does not expand the underlying filesystem or bucket. ownCloud warns that total data across spaces can fill the storage filesystem even when individual space quotas are configured. Partially uploaded files may also temporarily occupy the upload area before they are moved into a target space. Review oCIS general storage considerations alongside per-space limits.
When the user approaches or reaches the new allowance, they may be unable to add more content to that space. Avoid promising that lowering a quota will automatically delete files: the documentation cited here describes assignment and quota behavior, but does not state that an administrator’s reduction purges existing content. Check current usage first, warn the user, and verify how your deployed release behaves before lowering a limit below current usage.
No. In the oCIS 9.0 configuration documentation, OCIS_SPACES_MAX_QUOTA is described as a global maximum quota for spaces, expressed in bytes; zero means unlimited. The documentation also says that if this global variable is not used, FRONTEND_MAX_QUOTA must be defined in the frontend service. These are deployment-level controls and capability limits, not the ordinary per-user value you select in Web user management. See the oCIS 9.0 special-scope environment variable reference.
Use the Web user editor for an individual’s personal-space allowance. Change a global maximum only when you are intentionally changing the maximum available across spaces, and review the version-matched configuration for all affected services. Don’t paste a per-user amount into a global setting as a shortcut.
Yes, if users are provisioned through a compatible oCIS proxy configuration. The current proxy documentation describes a YAML role_quotas mapping that assigns a quota, in bytes, to new users based on their role ID. It specifically says this mapping is configured in YAML, not with environment variables. For example, the structure is:
role_quotas:
<role ID>: <quota in bytes>Replace both placeholders with values verified for your deployment. For instance, 10 GiB is 10,737,418,240 bytes when calculated as 10 × 1,073,741,824; use that number only if it matches your intended policy and the role ID is correct. This is an automatic assignment for newly provisioned users, not a documented bulk update for existing accounts. The proxy’s role-assignment mechanism may also depend on how your OpenID Connect provider supplies role claims. Read the oCIS 9.0 proxy service documentation and test with a noncritical new account before relying on it.
OCIS_SPACES_MAX_QUOTA is a global maximum in bytes. Action: set one user’s personal quota in user management.Ask the user to sign in and open the account information or settings from the round initials icon at the right side of the Web interface. ownCloud’s Web for Users documentation says this menu shows storage quota and usage. Confirm the displayed quota is the expected value, then have the user try a small upload if operationally appropriate. A successful small upload confirms access, not that the full quota is available, so continue monitoring backend capacity.
If the new value is missing, first sign out and back in, then recheck the edited account and the space involved. If the quota still differs, confirm that the account is managed by the Web UI rather than an external identity source, check the exact deployed versions, and review the applicable proxy, frontend, and storage configuration. The current public documentation does not define a single troubleshooting sequence for every identity-provider and storage backend combination; use the release-specific admin guide or your organization’s oCIS operator runbook for that part.
Compare seven tools that support or complement WSUS, from Microsoft’s native console and diagnostics to third-party patch publishing and remote deployment.
Compare six Windows system monitoring tools for server health, application visibility, and alerting, with current notes on deployment and licensing.
Compare seven Wake-on-LAN tools by features and availability, including free utilities, network-admin suites, and 2021 picks that have since been retired.
Compare nine ping tools for quick reachability checks, subnet discovery, TCP tests, and latency monitoring, with guidance on which one fits your network task.
Compare the best TFTP servers for Windows, Linux, and macOS, including SolarWinds, Tftpd64, tftpd-hpa, atftpd, haneWIN, and dnsmasq.
Compare five Microsoft Access alternatives for desktop, SQLite, no-code, and browser-based database work, with strengths, limits, and best-fit use cases.
Compare open-source and closed-source monitoring tools by cost, support, customization, security, and current options including Zabbix, Nagios, PRTG, and more.
Understand how ingress and egress describe incoming and outgoing traffic, why direction depends on the network boundary, and how to monitor bandwidth and spot risky data transfers.
Compare six free syslog servers and collectors for Windows and Linux, including GUI tools, open-source options, search, alerting, and secure transport.
See what Microsoft IIS does, how its request pipeline and application pools work, and when Apache, NGINX, or Caddy may fit your web server needs better.
