Workfront login data and Home configuration answer different questions: one shows sign-in activity, the other shapes what users see when they arrive. Read together, they give administrators a focused, repeatable way to decide which users and configuration to review next.
Overview
Most Workfront administrators review login information and the Home area for different reasons. Read together, they support a more focused review: login information can identify patterns in sign-in activity, while the assigned layout template and Home configuration show part of the experience a user may encounter. Neither one, by itself, explains why a person is or is not using Workfront.
This article connects those two perspectives. Use login information as a signal for deciding which users or groups may need a closer look, then review the landing page and Home configuration assigned to those users. The goal is not to treat Home as a proven cause or guaranteed solution, but to make the investigation more specific and repeatable.
Two tools that are easy to review separately
Login information and Home sit in different parts of an administrator's routine. You might review sign-in information during a user or license review, while Home and layout-template settings are more likely to come up during onboarding or configuration work. Because the tasks are often handled separately, the relationship between sign-in patterns and the configured user experience can be easy to overlook.
Login information can identify a pattern, but it does not explain the pattern. Home and layout-template settings can be reviewed and changed, but reviewing them without first identifying the affected users or group can make the work less targeted. Connecting the two creates a practical investigation path without assuming that one explains the other.
What Workfront login information can tell you
Workfront provides sign-in information through fields on the user record. By adding Login Count and Last Login Date to a user list or user report, an administrator can review the recorded login count and the most recent login date for each user. Login Count follows Workfront's documented counting method: a user's login activity is counted once per 24-hour period rather than once for every sign-in event.
These fields can help identify users with a low recorded login count or an older Last Login Date. They do not show what a user did after signing in, which features the user used, whether the user completed work, or why sign-in activity was low. They are indicators of sign-in activity—not a complete measure of usage, engagement, or adoption.
The system audit log is a separate tool with a different purpose. It records user-initiated changes in Workfront, including information about the action, the affected object, the user, and the date; depending on the event, additional information may also be available. Workfront documents the audit-log history as covering the previous 90 days, and the data can be filtered and exported for review.
That distinction matters. Login information helps an administrator review sign-in indicators. The audit log helps review recorded changes. The standard Workfront audit log should not be described as a complete record of successful logins, logouts, or failed login attempts.
The signal worth investigating
Suppose a group has low Login Count values or older Last Login Date values. That is a signal to investigate, not a diagnosis. The data does not identify the reason for the pattern, and it does not establish that the user's landing page or Home configuration caused it.
A reasonable next step is to identify the users' assigned layout template, landing page, and Home configuration. That review can show whether the configured entry experience is aligned with the work those users are expected to do. It can also reveal whether Home is part of their entry experience at all.
Why Home is not always the default landing page
Home can provide access to work through widgets. Depending on a user's license, access level, and configuration, Home may include items such as assigned tasks, issues, requests, and approvals. The available content and widgets are not necessarily the same for every user.
It is also important not to assume that Home is the first screen every user sees. Workfront's default layout and landing-page experience can vary by access level and license type. An administrator can also use a layout template to configure Home and specify a different landing page, such as another Workfront area or a dashboard.
There is a documented exception for Contributors and Requestors: when Requests is configured as the landing page, those users are shown Home instead. This behavior should be considered when reviewing a template assigned to either of those user types.
Before interpreting a sign-in pattern, identify two things: which landing page the assigned layout template specifies, and what the assigned Home configuration contains. Assuming that every user starts on the same Home experience can lead an administrator to review the wrong configuration.
Turning a sign-in signal into a focused review
The connection between login information and Home is best treated as an investigation loop. Login information helps identify where to look. The layout template and Home settings provide configuration context. A later comparison of login information can show whether the recorded sign-in pattern changed, but it cannot by itself prove why the change occurred.
A simple review can follow these steps:
-
Identify users or groups with a low recorded Login Count or an older Last Login Date.
-
Review the layout template assigned to those users and note the specified landing page.
-
Review the Home configuration and widgets available to the affected users.
-
If the configuration does not match the role's intended work, consider adjusting the layout template, landing page, or Home configuration.
-
Compare the same login fields later and record whether the sign-in indicators changed. Treat that comparison as an observation, not proof that a configuration change caused the result.
The value of this process is its discipline: start with a documented sign-in pattern, inspect the configuration that may shape the entry experience, and separate what the data shows from what still requires investigation.
What to review, and what the data supports
-
When users have a low Login Count or an older Last Login Date, review the layout template assigned to those users and its landing page, and check whether the configured entry experience matches the group's intended work.
-
When users have recent sign-in records but unknown post-login activity, remember that login information does not show what happened after sign-in; other data or processes are needed to assess work activity. Avoid treating recent sign-in activity as proof of feature use, task completion, or adoption.
-
When only a subset of a team has recent sign-in information, check whether those users share a layout template and whether the relevant configuration is consistent across the group, then review the group's template assignment and consider whether a role-specific configuration is appropriate.
-
When Contributor or Requestor users are associated with a Requests landing-page configuration, account for the documented Requests behavior for those user types: those users are shown Home when Requests is configured as the landing page.
Putting it into practice
A short, repeatable review is more useful than treating login information as a one-time audit. For example:
-
Add Login Count and Last Login Date to a user report and review the values on a regular schedule.
-
Group users by role or team so that a sign-in pattern can be reviewed in context.
-
For a group that warrants review, open the assigned layout template and note its landing page and Home configuration.
-
If the configuration does not fit the intended work, consider an appropriate adjustment and confirm which users receive the template.
-
Compare the same login fields later and document what changed, without treating the comparison as a complete adoption measurement.
-
This approach creates a consistent way to connect sign-in information with configuration review. It does not replace broader measures of Workfront usage, and it does not establish that a Home or layout-template change caused a later change in sign-in activity.
Frequently asked questions
Where do I find login information in Workfront?
Add the Login Count and Last Login Date fields to a user list or user report. Use the system audit log separately when you need to review recorded user-initiated changes; it is not a complete authentication history.
How long is audit-log data kept?
Workfront documents the audit-log history as covering the previous 90 days. That retention statement applies to the audit log; it should not automatically be applied to the Login Count or Last Login Date fields.
Is Home the first screen every user sees?
No. The landing-page experience can vary by access level, license type, and layout-template configuration. An administrator can configure a different landing page through a layout template.
Can I set a different landing page for one team without changing everyone?
Yes. An administrator can create or use a layout template, configure its landing page and Home settings, and assign the template to the relevant users.
Why do Contributor or Requestor users still see Home when Requests is configured as the landing page?
That is the documented behavior for those user types: when Requests is the landing page, Contributor and Requestor users are shown Home instead.
Resources
The article's product-behavior statements are based on the following Adobe Workfront documentation. References are consolidated here rather than repeated throughout the article.