This article explains how to manage members within your AgentRunner workspace. Understanding member roles and permissions is crucial for maintaining a secure and collaborative environment. Whether you're inviting new team members, adjusting their roles, or understanding access privileges, this guide will provide you with the necessary information to effectively manage your workspace members.
Understanding the Members Menu and Roles
The Members menu in AgentRunner is where you manage who has access to your workspace and what they can do. You can invite new members and adjust their roles, which determine their level of access and control within the workspace. AgentRunner offers three distinct roles: Owner, Developer, and Operator. Each role has specific privileges designed to streamline collaboration while maintaining security. This section will delve into the location of the Members menu and elaborate on the responsibilities associated with each role, ensuring a comprehensive understanding of user management within AgentRunner. Knowing the difference between each role will help you to correctly assign members the permissions they require to effectively contribute to your projects and agents.
Accessing the Members Menu
The Members menu is accessible from anywhere within the AgentRunner platform, except the agent editor. To access it, navigate to the main menu and look for the "Settings" menupoint. From there, you can easily find the Members menu. This centralized location allows you to quickly manage your workspace members without disrupting your workflow.
Roles and Privileges
AgentRunner offers three distinct roles:
Owner: Owners have unrestricted access to anything and everything within the workspace. They possess complete control over all settings, projects, agents, and member permissions.
Developer: Developers have extensive access, allowing them to manage workspace settings, as well as edit and run projects and agents. However, they cannot access member permissions or request API keys for agents.
Operator: Operators have the most restricted access, with the ability only to run agents. They cannot access workspace settings, edit projects or agents, or manage member permissions.
Inviting and Managing Members
Inviting new members to your AgentRunner workspace is a straightforward process. This section will guide you through the steps to invite new members, including the required information and the process for assigning roles. Additionally, we will cover how to modify member roles and the implications of each role change. Understanding these processes is essential for maintaining a well-managed and secure workspace. By following these instructions, you can ensure that your team members have the appropriate access levels to contribute effectively while safeguarding your workspace.
Inviting New Members
To invite new members to your AgentRunner workspace:
Open the Members menu. (See section above about how to access the Members menu.)
Click on the Invite member button.
Enter the new member's email address.
Click Add.
Optional: Select their role from the dropdown menu. If you skip this, you can modify it later.
Recommended Visual: A screenshot of the "Invite member" form with the email address field and role selection dropdown highlighted.
The new member will be automatically added to the workspace and can begin using it immediately without needing to confirm.
Expected Outcome: The new member is added to the member list with the selected role (or a default role if none was selected).
Adjusting Member Roles
The owner can change anyone’s roles in the members menu:
Open the Members menu. (See section above about how to access the Members menu.)
Find the member whose role you want to change.
Select the new role from the dropdown menu next to their name.
Recommended Visual: A screenshot of the member list with the role selection dropdown highlighted for a specific member.
The member's permissions will be updated immediately to reflect the new role.
Expected Outcome: The member's role is updated in the member list, and their access privileges within the workspace are adjusted accordingly.
Important Considerations for Member Roles
A member can only have one role at a time.
There is no limit to the number of members that can be invited to a workspace.
Only grant the owner role to trusted people within your company.
Understanding Role-Specific Access
The different roles within AgentRunner are designed to provide varying levels of access and control. It's important to understand the specific capabilities and limitations of each role to effectively manage your team and maintain workspace security. This section will further clarify what Owners, Developers, and Operators can access and do within AgentRunner. It will also explain the implications of certain restrictions, such as Developers not being able to request API keys. By understanding these nuances, you can ensure that each member has the appropriate permissions to perform their tasks efficiently and securely.
Owner Permissions
Full Access: Owners have unrestricted access to anything and everything within the workspace.
Member Management: Owners can invite, remove, and modify the roles of all members, including other Owners.
API Key Generation: Owners can request API keys for the projects.
Developer Permissions
Workspace Settings: Developers can access and modify workspace settings.
Project and Agent Management: Developers can create, edit, and run projects and agents.
API Key Restriction: Developers cannot request API keys for projects, which restricts their ability to integrate it into another website.
Operator Permissions
Agent Execution: Operators can run agents.
Limited Access: Operators cannot access workspace settings or view the design or logic of a agent; they are only able to execute it.
No Editing: Operators cannot create or edit projects or agents.
