Journyx cloud timesheet
Journyx is a premier time tracking software for businesses that need to easily and accurately track employee time for projects, billing, and payroll. Our time tracking solutions are designed especially for organizations that deliver project-oriented or client-oriented work. We help thousands of companies worldwide save time and money by streamlining the collection and processing of timesheets.
Journyx offers two core products that enable customers reach their maximum level of profitability: Journyx JX Time Tracking Software (for project or activity-based time and expense tracking) and Journyx PX Resource Management Software (for a complete picture of project and budget status, employee time, and resource availability). PX includes all the great features of JX, plus more tools to help you forecast and allocate resources, manage project costs, and oversee complex project schedules.
With Journyx, you can easily create detailed time and expense reports to get the data you need, when you need it. Our industry-leading time tracking software is highly customizable, easy to use, and integrates seamlessly with most other business systems to offer you more efficient accounting, auditing, and billing. Journyx integrates with Microsoft Dynamics (NAV, GP, SL, AX, 365), Microsoft Project, QuickBooks, Sage Intacct, ADP, Oracle Netsuite, SAP, and more!
Whether you categorize work by projects, clients, tasks, or some other job type, Journyx offers valuable insights into where your business is investing labor time and money, so you can make better, more informed decisions. Journyx is highly customizable, easy to use, and helps your team work more efficiently and reduce timesheet, billing, and payroll errors.
- OIDC OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service provider (SP) and does not require credentials to be passed from the Identity Provider to the application.
- SAML Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP) that does not require credentials to be passed to the service provider.
- SWA Secure Web Authentication is a Single Sign On (SSO) system developed by Okta to provide SSO for apps that don't support proprietary federated sign-on methods, SAML or OIDC.
- Attribute Sourcing
- Create Creates or links a user in the application when assigning the app to a user in Okta.
- Update Okta updates a user's attributes in the app when the app is assigned. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.
- Deactivate Deactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Accounts can be reactivated if the app is reassigned to a user in Okta.
- Sync Password Push either the users Okta password or a randomly generated password to the app. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password.
- Group Push Push existing Okta groups and their memberships to the application. Groups can then be managed in Okta and changes are reflected in the application.
- Group Linking Link Okta groups to existing groups in the application. Simplifies onboarding an app for Okta provisioning where the app already has groups configured.
- Schema Discovery Import the user attribute schema from the application and reflect it in the Okta app user profile. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema.
- Attribute Mastering The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.
- Attribute Writeback When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.