Roles
We define who needs to edit products, documents, courses, pages, or settings, and which permissions go with each responsibility.
Services › Impact and evolution › Team training
Team training
We prepare the people who will use and maintain the digital structure to handle routine tasks on their own: adding products, updating documents, publishing content, and recognizing when a change needs a different level of intervention.
Training is built around the real system and each team's responsibilities, rather than a generic tour of every feature in a tool.
The site stays in the hands of the people who use it every day.
Training is organized around tasks, not buttons.
Additions and changes
The team practices with real tasks: adding a product, filling in fields, linking content, replacing documentation, or updating a date.
Publishing
The team learns which statuses exist, what to check before publishing, and where validation workflows fit in.
Criteria
We document decisions that aren't obvious from the interface: which field is used for each piece of data, how files are named, when to create a category, and when to reuse an existing one.
Limits
We also make clear what shouldn't be changed without technical support and which changes need medical, regulatory, or other review.
Support material
The documentation focuses on the tasks that will actually be repeated, so it can be used after the session.
How it's prepared
Training starts before the meeting.
Tasks
We identify what each role needs to handle during the first weeks of operation.
Environment
We prepare examples and check permissions so the team can practice on a structure that is safe and easy to understand.
Session
The training covers real tasks and gives the team time to perform them directly.
Adjustments
The questions that come up can reveal confusing fields, unnecessary steps, or documentation worth improving before the handoff is complete.
Work · SAI
The idea was for the team to be able to manage the site's content.
The structure built for SAI was designed so the company could manage its own products, documentation, courses, and content.
FAQ
After the project, does the company depend on Audacher to publish a product page?
No. The site is built and handed over for the team to run. Structural changes still require development, such as adding a field to a product page or a new content type, and the company can choose who handles that work.
Can products be added and edited without calling a developer?
Yes. That's the goal of both the development and the training: adding a product, replacing a document, or publishing a course are tasks for the team.
What happens when someone new joins the team?
They learn from the site's guides and recordings. If they have a different role, or if the site has changed a lot since the last training, there's a refresher session.
What needs to happen after launch for the team to actually use the site?
The team handles the first uploads with us there to support them. The launch includes a piece created for the internal team, and questions from the first few weeks are collected and answered in a session.