Overview
The TwikBot Platform uses an organisation-based account structure with role-based access control. Understanding how organisations, users, and roles are structured is essential before setting up a new client account or onboarding team members to an existing project.
Organisations
An organisation in TwikBot is the top-level container for all platform activity — products, projects, commerce data, and users. Each client you implement for will have their own organisation, and you as a partner or agency will typically operate across multiple organisations.
Managing Multiple Organisations
Partners and agencies with access to multiple client organisations can switch between them using the organisation dropdown in the account section at the bottom of the navigation menu. Always verify the active organisation before creating or modifying products, projects, or user accounts.
Setting Up a New Organisation
When onboarding a new client, a new organisation is created within the TwikBot Platform. Contact the Twikit team via support.twikit.com to provision a new client organisation.
Users
Users are individual accounts within an organisation. Each user has a set of permissions determined by their assigned role. Users can be added and managed from the Account Management section of the TwikBot Platform.
Adding Users
To add a new user to an organisation:
-
Navigate to Account Management in the TwikBot Platform
-
Create a new user account with the appropriate email address
-
Assign the relevant role based on what the user needs to access and do within the platform
User Considerations
-
Only assign the level of access a user genuinely needs — avoid granting broad permissions as a convenience
-
For client handover, ensure that the client's designated administrator user has the appropriate role to manage their own users post-handover
-
Partner and agency team members working across multiple client organisations will need a user account in each organisation
Roles & Permissions
Roles in TwikBot control what a user can view and do within the platform. Assigning the correct role to each user is important for both security and operational clarity — particularly when clients take over day-to-day platform management after go-live.
General Principles
-
Implementation team members (partners, agencies) typically require broad access during the build phase, including product editing and project management
-
Client administrators require access to manage their own users and review commerce activity, but may not need access to product editing post-handover
-
End users or sales staff accessing commerce data (configurations, quotes, orders) require the most restricted role set
Account Security
-
Always log out of the platform when your session is complete, particularly when working across multiple client organisations
-
Use organisation switching rather than sharing credentials between team members
-
Keep user accounts up to date — remove access for team members who are no longer active on a project