Getting Started

Every procurement team has their own ways of working and best practises. Axiom provides your team with the ability to configure the system to work in the way you want it to work. This all starts with deciding who can do what.

There are three ways you can decide what your uses can do:

1. Roles
2. Approval Permissions
3. Buyer Permissions

When deciding on your roles you should first identify the key roles needed for each functional area of your organisation and then clearly outline their responsibilities, for example:

• Category managers: Responsible for onboarding and managing suppliers, managing price and product changes, analysing supplier performance etc.
• System administrators: Responsible for administering the platform, inviting new users, managaging roles and permissions etc.
• Buyers: Responsible for buying products, managing their wish lists, reseting their password etc.

The size of your procurement department will influence the number and specificity of roles. Smaller procurement departments may require individuals to wear multiple hats, while larger departments might involve more specialized roles. Document the defined roles and responsibilities. This documentation can serve as a reference for team members and can be updated as needed.

Once this is done you should establish communication channels and protocols to ensure effective cross functional collaboration. This might involve regular team meetings, daily stand-ups, and documentation. Stay aware that roles may need to evolve as the system develops. Encourage a culture of adaptability and flexibility to handle changing requirements and priorities. We would advise to periodically review the roles and responsibilities to ensure they align with the evolving needs of the project. Makeing adjustments as necessary to optimize team efficiency.

More information on how to use roles functionality can be found here.

Approval permissions are specified on a user level, generally these permissions will be granted to your category managers or catalogue managers. These permissions determine which users have the ability to approve products into the marketplace as well as price changes and new promotions.

It is recommended that a system administrator is given the ability to assign approval permissions and that there is always more than one user who has the ability to approve a product/price/promotion.

More information on approval permissions can be found here.

Buyer permissions determine what different users can see and buy in the shop. These permissions are usually set up by category managers or system administrators as they often involve regulatory constraints e.g. only certain users can buy Personal Protective Equipment.

It is recommended that a system administrator is given the ability to create buyer permissions to make sure all regulatory constraints are applied correctly.

More information on how to setup buyer permissions can be found here.