> ## Documentation Index > Fetch the complete documentation index at: https://docs.getveles.com/llms.txt > Use this file to discover all available pages before exploring further. # Adding Users > Add team members to Veles, assign roles and permissions, configure the org hierarchy, and control product visibility with filters. User management in Veles is handled in the **Admin Console** under the **Access** section. Here you control who can access the platform, what they can do, and which products and data they see when building quotes. Only users with the **Admin** role can add or manage other users. *** ## Creating a new user Navigate to **Admin Console > Access > Users** and click **+ Add New User**. ### Personal details | Field | Required | Description | | --------------------- | -------- | ---------------------------------------------------------- | | **First & Last Name** | Yes | The user's display name throughout the platform. | | **Email Address** | Yes | Their login identifier. The invitation email is sent here. | | **Job Title** | No | Useful for internal context and reporting. | | **Phone** | No | Optional contact info stored on the user record. | ### Manager Select the user's direct manager from the dropdown. This field is optional but important -- it drives two things: 1. **Approval routing.** When a quote requires approval, Veles automatically identifies the rep's manager as the approver. If you don't set managers, you'll need to configure approval chains manually. 2. **Org chart.** The manager relationship builds your team's reporting structure, which you can view visually by toggling the **Org Chart** view at the top of the Users table. Set up your managers and org hierarchy before configuring [Approval Workflows](/get-started/calculator/approvals). The approval engine uses this hierarchy to determine routing, so getting it right upfront saves you from debugging approval chains later. ### Role Every user is assigned one of three roles that control their access level: Admins have unrestricted access to the entire platform. This includes: * Full access to the Admin Console (settings, integrations, price books) * Create, edit, and delete users * Configure pricing rules, approval workflows, and document templates * Create and manage quotes, orders, and contracts * View all reporting and analytics **Who should be an Admin:** RevOps leads, deal desk managers, and the team member responsible for maintaining the Veles instance. Keep this group small. Members are the core user role for anyone actively building quotes and working deals. They can: * Create and edit quotes * Add products from the catalog and configure pricing options * Link quotes to CRM opportunities * Send quotes to buyers via the web portal * View their own quotes and deals Members **cannot** access the Admin Console, change global pricing logic, edit the product catalog, or manage other users. **Who should be a Member:** Account Executives, Sales Reps, Sales Engineers, and anyone who creates or edits quotes. Viewers can see commercial data but cannot create or modify anything. They can: * View quotes, orders, and contracts * Access dashboards and reports * Review deal details and pricing Viewers **cannot** create quotes, edit pricing, or access admin settings. **Who should be a Viewer:** Finance, Product, Customer Success, and any stakeholder who needs visibility into deal data without the ability to change it. *** ## Assigning filters After setting the role, you can assign the user to one or more **filters**. Filters control which products and data a user sees when building quotes, ensuring reps only work with products relevant to their deals. ### Segments Assign the user to customer segments like **Enterprise**, **Mid-Market**, or **SMB**. When a product is tagged with a segment, only reps assigned to that segment will see it in the catalog during quoting. ### Regions Assign to geographical territories like **North America**, **EMEA**, or **APAC**. Region filters work the same way as segments -- products tagged with a region are only visible to reps assigned to that region. ### Custom filters If your organization has created additional filter dimensions (e.g., **Vertical** with values like "Healthcare" or "FinTech"), you can assign users to those as well. Filters are additive. A rep assigned to "Enterprise" and "North America" will see products that match either filter, not just products that match both. If a product has no filters set, it's visible to all reps. *** ## Managing existing users ### Editing a user Navigate to **Admin Console > Access > Users** and click on the user you want to edit. You can update any field: name, email, job title, manager, role, or filter assignments. Changes take effect immediately. ### Changing a user's role To change a user's role (e.g., promoting a Member to Admin), edit the user and select a new role from the dropdown. The new permissions apply on their next page load. ### Deactivating a user When someone leaves the team or no longer needs access, deactivate their account rather than deleting it. Deactivation preserves their historical data (quotes they created, approvals they gave) while preventing further login. If a deactivated user was a manager in the org hierarchy, their direct reports will need to be reassigned to a new manager. Otherwise, approval routing for those reports may break. *** ## The org chart Veles builds a visual org chart from the manager relationships you define on each user. To view it, go to **Admin Console > Access > Users** and toggle the **Org Chart** view at the top of the table. The org chart serves two purposes: it gives leadership a quick view of team structure, and it's the source of truth for approval routing. If your approval workflows use manager-based routing, the org chart is where Veles determines who approves what. *** ## What's next Configure the approval chains that use the org hierarchy you just set up. Sync users and deal data with Salesforce or HubSpot. Build your product catalog so your team has something to quote. Set up pricing guardrails before reps start building deals.