docs: restructure user permissions documentation to clarify roles and access levels

- Updated the permissions section to define three distinct user roles: Owner, Admin, and Members, each with specific capabilities and limitations.
- Enhanced the description of permissions available to Members, detailing actions they can perform.
- Improved clarity on project permissions and the ability to assign access at the environment level for granular control.

Author: Mauricio Siu

apps/docs/content/docs/core/(Users)/permissions.mdx

@@ -3,24 +3,53 @@ title: Permissions
 description: 'Add permissions to your users to manage your applications and services.'
 ---
 
-Manage user roles and permissions within Dokploy. Note that only one admin role is allowed per instance.
+Manage user roles and permissions within Dokploy. Dokploy handles three distinct roles with different levels of access and capabilities.
 
-## Permissions
+## Roles
 
-Dokploy offers multiple permissions to manage your users effectively:
+Dokploy supports three roles for managing user access:
 
-- **Create Projects**: Allows the user to create new projects.
-- **Create Services**: Allows the user to create new applications or databases.
-- **Access Traefik Files Tab**: Allows the user to access the Traefik files tab.
-- **Delete Projects**: Allows the user to delete projects.
-- **Delete Services**: Allows the user to delete services.
-- **Access Docker Tab**: Allows the user to access the Docker tab.
-- **Access API/CLI**: Allows the user to access the API/CLI, including the Swagger route.
-- **Access to Git Providers**: Allows the user to access the Git Providers.
-- **Access to SSH Keys**: Allows the user to access the SSH Keys.
+### Owner
+
+The **Owner** is the creator of the organization and has the highest level of access:
+
+- Full administrative privileges
+- Can perform all actions that admins can do
+- Can delete and edit the role of admins
+- **Intransferable**: The owner role cannot be transferred to another user
+- Only one owner exists per organization
+
+### Admin
+
+**Admin** users have extensive administrative capabilities:
+
+- Can perform all actions that the owner can do
+- Full access to all features and settings
+- **Limitations**: Cannot delete or edit the role of other admins
+- **Limitations**: Cannot delete or edit the role of the owner
+
+### Members
+
+**Members** are regular users who have access based on the permissions assigned to them. Members can be granted specific permissions to manage applications and services.
+
+#### Permissions
+
+The following permissions are available for **Members** to manage your users effectively:
+
+- **Create Projects**: Allow the user to create projects.
+- **Delete Projects**: Allow the user to delete projects.
+- **Create Services**: Allow the user to create services.
+- **Delete Services**: Allow the user to delete services.
+- **Create Environments**: Allow the user to create environments.
+- **Delete Environments**: Allow the user to delete environments.
+- **Access to Traefik Files**: Allow the user to access to the Traefik Tab Files.
+- **Access to Docker**: Allow the user to access to the Docker Tab.
+- **Access to API/CLI**: Allow the user to access to the API/CLI.
+- **Access to SSH Keys**: Allow to users to access to the SSH Keys section.
+- **Access to Git Providers**: Allow to users to access to the Git Providers section.
 
 You can also grant permissions to specific users for accessing particular projects or services.
 
-### Project Permissions
+#### Project Permissions
 
-Based on your projects and services, you can assign permissions to specific users to give them access to particular projects or services.
+Based on your projects and services, you can assign permissions to specific users to give them access to particular projects or services. You can also select specific environments within projects, allowing you to grant granular access control at the environment level.