When an existing Agent is added to a new Project, by default, the Agent receives the same user role that he has in his default (or first) Project. It is possible to make an Agent (or user with another custom Agent-type role) a Customer in another Project. This allows the user to act as an Agent in their default project, creating Issues, getting assigned to Issues, adding to the Knowledge Base, etc., while allowing him to submit Requests as a Customer in another project.
To make an Agent a Customer in the current Project:
The user is now a Customer in the current Project, but still an Agent in his default Project.
Note
When an Agent changes to a project in which he is a Customer, he can switch back to a project in which he is an Agent without having to log in again. If the user is a Customer in multiple projects, he must first switch back to a project in which he is an Agent to have access to the other Customer projects. This prevents conflicts with Address Books that have different primary keys.
Note
If a user is a customer in one Project and an Agent in another Project, the Agent Project will always became that user's default Project. Also, when you add a customer to a Project and set the role to an Agent role, the new Project will be automatically selected as the default.