# Granting access

!!! note "Changes as of May 4, 2026"
    Previously, permissions were managed using `NamespaceUser` and `NamespaceGroup` objects. **These objects are now
    replaced by a single `NamespacePermissions` object inside your namespace.** Previous permissions have been migrated,
    please make sure to update your stored YAML manifests.

Similar to [requesting a project](https://datalab.tuwien.ac.at/de/infrastructure/openshift/creating-a-project/), you can also self-manage access to your project. You can manage the permissions
in your namespace by editing the `NamespacePermissions` object in your namespace. You can do this, for example, by using
`oc edit nsp <namespacename>` and adding the following content:

```yaml
apiVersion: tuwien.ac.at/v1
kind: NamespacePermissions
metadata:
  name: project-test
  namespace: project-test
spec:
  owner: someuser
  users:
    user1: admin
    user2: edit
    user3: view
  groups:
    group1: admin
    group2: edit
    group3: view
```

!!! tip
    Editing `NamespacePermissions` resources requires *admin* access to the project.

!!! tip
    You cannot change the `owner` field in the `NamespacePermissions` resource. Contact us
    if you need to change or delete a project.

!!! tip
    You can create standard Kubernetes `Role` and `RoleBinding` objects independently of the TU Wien
    `NamespacePermission` objects. However, these will not grant users access to features like ArgoCD. Use `Role` and
    `RoleBinding` objects to create service accounts, but `NamespacePermissions` for human users.