Before proceeding any further, double-check if your existing workspace in Timeneye is ready to welcome the rest of the company. Make sure you go through the following points to set up the best possible workspace:

  1. Create or import all your real-life projects

  2. Create and assign clients to those projects, if required

  3. Create new Phases or Tags, if you need a further categorization

  4. Decide the hierarchy of each Group and assign roles and permissions accordingly

  5. Decide the naming conventions for Groups, Projects, Phases and Tags

Once your workspace is set up, you can start inviting people to join you from the Teams section in the sidebar menu of the Dashboard.

When you are ready, right under the green “New team members” button, you’ll see the options to import your team members automatically from Microsoft or Google Workspace. If your team uses Office 365 or Google Suite, we’ve got you covered!

Timeneye also offers SSO through SAML identification, to provide you with an extra level of control and security as you scale the software to the whole company.

Automatically, they will receive an invitation email and support material about how to get started with Timeneye, according to their role.

Additional resources: How to manage remote teams

Keep the communication channels open

The small-scale pilot should have troubleshot the most pressing issues, but in the Scale Phase some other road bums could come up. Hopefully this time you should be able to intercept those oddballs promptly.

Good practices for a smooth onboarding are:

  • Make sure the new business units are in contact with the internal Help Desk or IT specialist, in case of technical problems;

  • Encourage all employees to reach out to their Group Manager or Admin for further training or technical assistance;

  • Give everybody access to the channel on your Microsoft Teams or Slack where people could ask questions and exchange tips and opinions;

  • Empower your early adopters and delegate to them the responsibility of training their peers by organising demo sessions.

Next: Monitor the team's usage & gather feedback

Did this answer your question?