Feature Availability¶
Use this page when a Browser context, bucket, or object action is missing.
What Browser availability depends on¶
Standalone Browser only shows storage contexts you are allowed to use. The operations inside a context are then limited by the endpoint capabilities and the S3 permissions of that context.
| What is missing | Check first |
|---|---|
| Browser workspace | Browser is enabled for your user. |
| A private connection | The connection is active, owned by you, and enabled for Browser. |
| A Portal project context | The project is available to you and Browser access for that Portal context is enabled. |
| A bucket | The selected context can list or open that bucket. |
| Upload, copy, move, or delete | The selected credentials have the required S3 permissions. |
| Direct browser transfer | The bucket CORS configuration allows the BucketReef origin; multipart uploads also need ETag exposed. |
| Previous versions | Bucket versioning is enabled and the selected credentials can list versions. |
| Advanced object actions | The Browser profile and endpoint capabilities expose the action. |
Embedded Browser experiences inside Manager, Portal, or Ceph Admin follow their host workspace rules and are documented in those guides.
What to do¶
- Confirm the selected Browser context and bucket.
- Refresh the bucket before retrying a write that returned an uncertain result.
- Read any S3 error shown by the operation.
AccessDeniedmeans the storage identity does not permit the requested action. - For upload or download failures, check the transfer details and, when direct transfer is used, the bucket CORS configuration.
- Ask an administrator to review Browser access only when the workspace or context itself is missing.