Picture a law practice in Nova Gorica with twenty-five people that moves its case files off an in-house server and into Microsoft 365. Technically, nothing goes wrong. Seven days on, though, half the lawyers still save pleadings to the desktop and push them back up as “pleading_final_3.docx”, trainees cannot tell which Teams team a case lives in, and client papers keep travelling through private messaging apps. At reception nobody knows whose PC has the qualified digital certificate used for court filings. Nothing is broken. The practice simply needs a person who guides the team through the new setup with its actual case files, folder tree and habits. This is the kind of company training Apply delivers: live, purely online through Teams or Google Meet, on your systems rather than a demo tenant. Lawyers at the main office, colleagues at a branch and anyone working remotely sit in one session, so there is no travel. We also do not guess the agenda; it comes from where your people genuinely struggle.
You will not find a fixed course catalogue here. These are the requests we hear most, and every one is reworked using your templates, shared drives and applications.
Several people editing one file at once instead of attachments ping-ponging by email, a sensible structure of Teams teams or shared drives, an outside contractor's link that expires automatically, and rolling back a file someone overwrote yesterday.
A text claiming a parcel is stuck until you pay a small fee, an email about an “income tax refund” that imitates FURS, a fake bank alert, a rushed transfer request supposedly from the managing director, and a supplier invoice whose IBAN has been swapped. The session also covers the first steps to take right after a bad click.
When Copilot, ChatGPT or a similar assistant genuinely helps and which house rules apply. Why personal data about clients or patients should never be pasted into a prompt, what the Information Commissioner recommends here, and how the EU AI Act links AI use to staff competence.
Which person holds which qualified digital certificate, why neither the certificate nor its password should live on a reception PC everyone shares, how authorisations in eDavki and on AJPES are arranged, and what to do before a certificate runs out.
Screenshots dropped into group chats, a forgotten printout, a message to the wrong recipient. Since a controller normally has 72 hours to notify the Information Commissioner of a breach, we practise exactly whom staff alert and how quickly.
Summarising data with PivotTables, cleaning imports with Power Query, then a first Power BI report fed by the spreadsheets a colleague currently merges manually each week from Minimax, Pantheon or webshop exports.
Connecting through the company VPN, securing your own router, a screen that locks itself, shredding papers you printed at the kitchen table, and what your written home-working agreement under ZDR-1 says on these points.
We shape the programme around problems your staff really have. Session dates fit your calendar, and we keep away from month-end and seasonal rushes.
Where Apply already handles your support, we review which tickets came in most often lately; otherwise attendees answer a five-question form. People are grouped by what they already know rather than by seniority.
One department goes first. Its feedback tunes the examples and the pace before the remaining teams are booked.
We talk little and let attendees do a lot, each on their own screen. Interrupting with questions is encouraged, and anything risky happens in a sandbox folder or test account, never on live data.
A brief question round some weeks later. If we look after your support, you see figures showing how requests on the trained subjects have shifted.
The goal of a simulated phishing email is faster reporting, not a list of culprits. Someone who falls for the bait and tells IT five minutes later shows the training has done its job. Someone scolded for it learns to stay silent, and the next incident is discovered days too late. Given the 72-hour window for notifying a breach under GDPR, that difference counts. Every session therefore closes with “You clicked. Now what?”, and nobody leaves without knowing the reporting route.
No. We are not an accredited educational institution and issues neither certificates nor officially recognised documents. If you wish, we send an informal list showing who attended, when, for how long and on which topics, for your internal training records on security or data protection.
On everything that surrounds them, yes: who may see what, pulling reports out to a spreadsheet, how the data gets backed up and shared. Deep specialist areas like salaries or costing are better taught by the software maker or one of its authorised partners tends to be the right teacher.
Yes, some weeks after training and only under rules management has signed off in writing. We report results by department, never by individual, because the point is to track improvement rather than embarrass anyone.
It is, as long as everyone is told in advance. Because a video captures personal data, set a retention period and limit who can open it. Participants may keep cameras switched off without explaining themselves.
Preparation and delivery are charged at €50 an hour, with VAT added. A written quote for the entire programme reaches you before the first session.
List the departments, what each should be able to do afterwards and the tools involved. You will get a programme using your own examples, proposed dates and a quote.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.
