Kuika’s project-based user management allows you to manage the roles and access permissions of users in your projects in detail. By customizing user permissions, you can make your project process more efficient. In this tutorial, you’ll learn how to manage users in your projects.

Adding Users with Different Roles to a Project

1. Log in to the Kuika platform and go to the Apps screen.
2. Open the three-dot menu next to the project to which you want to add a user.
3. Click the Edit option.
4. In the window that opens, go to the Share tab.
5. Select the user you want to add from the Add User drop-down list. By default, each added user is assigned the Viewer role.
6. Select the appropriate role from the drop-down menu next to the username:
   
   • Viewer: Can only view the project.
   • Developer: Can use the Datasources, Workflow, Scheduled Jobs, and Config Manager modules.
   • Designer: Can only view these modules.

Sharing the Project with a Workspace

1. Log in to the Kuika platform and go to the Apps screen.
2. Open the three-dot menu next to the project you want to share.
3. Click the Edit option.
4. In the window that opens, go to the Share tab.
5. Select the access type from the Public Access drop-down menu:
   
   • Restricted: Only added users can access the project.
   • Everyone in workspace: The project can be viewed by all users in the workspace.

Removing a User from a Project

1. Log in to the Kuika platform and go to the Apps screen.
2. Open the three-dot menu next to the project from which you want to remove a user.
3. Click the Edit option.
4. In the window that opens, go to the Share tab.
5. Open the dropdown menu next to the user you want to remove and click the Remove User option.

Transferring Project Ownership

1. Enable the Enable workspace authorization option.
2. Apps screen, open the three-dot menu next to the project you want to transfer.
3. Transfer Ownership.
4. In the window that opens, enter the name or email address of the user to whom you are transferring the project.
5. Click the Confirm Ownership Transfer button to complete the transfer.

Transferring Member and Role Relationships When a Project Is Duplicated

When a project is duplicated, the member and role relationships from the source project are automatically transferred to the duplicate project. Roles defined in the source project—such as Viewer, Developer, and Designer—and the associated users are carried over to the new project in the same manner.

Thanks to this behavior:

• User access continues seamlessly after the project is duplicated.
• You do not need to recreate the authorization structure from the source project.
• Members’ roles in the copied project can be further edited via the Share tab as needed.

Advanced Authorization with Generated App Roles

With Kuika’s authorization system, you can define Generated App roles specific to your projects. These roles can include multiple permission groups and component permissions.

Features:

• Invisible in the Designer environment; defined within the project.
• Follows the Component > Permission Group > Generated App Role hierarchy.
• Role creation and editing are performed from the permission management page within the application.

Application steps:

• After adding a user, you can specify their access by assigning a Generated App role.
• Each Generated App role includes the permission to view or interact with specific components within the application.
• This structure provides personalized and advanced permission control for each user.

Roles defined in projects can also be managed at the workspace level via the Settings > Roles screen. From this screen, you can see which projects a role is used in, add the role to other projects or remove it from projects, and rename the role across all projects where it is used in a single operation. For more information, see the Managing Roles at the Workspace Level section in the Workspace User Management document.

Editing User Permissions

You can manage users’ access permissions in detail using the permission management page created within the application:

• Generated App roles, permission groups, and component permissions assigned to the user are displayed.
• Permissions can be selected from a hierarchical component list.
• Role and permission conflicts are checked; changes cannot be made to parent roles without first deleting dependent permissions.
• Updates are automatically applied to the relevant user.

Thanks to this structure, project authorization processes in Kuika become more flexible and customizable. You can establish a robust access management infrastructure with component-based control and user-specific access configuration.