Activity Feed: How to Review Actions and Changes in Diamond Operations Pro

What the activity feed is used for

The "Activity Feed" is used to review system-recorded events and understand the sequence of actions performed by users.

It can help answer questions such as:

• Who created a record?
• Who edited information?
• Who deleted a record?
• When did a change happen?
• Which user sent an action?
• What happened before or after an unexpected change?
• What recent activity exists for a job, client, or another module?

This module is especially useful when information needs to be confirmed, changes need to be investigated, or a reported situation requires follow-up.

Who should use this module

The "Activity Feed" is intended for users who need to review or audit actions within the system.

It is usually used by:

• Administrators.
• Supervisors.
• Owners.
• Users responsible for internal audits.
• Users who investigate record changes.
• Authorized staff who review system activity.

Because this module can show information related to user actions, it should only be available to people with review or supervision responsibilities.

When to use the "Activity Feed"

Use this module when you need to investigate or confirm actions performed in the system.

Common cases include:

• You need to know who created a record.
• You want to review who edited information.
• You need to confirm whether a record was deleted.
• A user reports an unexpected change.
• A client asks about a modification.
• Recent activity is being audited.
• Sent, created, or modified actions need to be reviewed.
• You need to understand the sequence of events in jobs or other modules.
• There are many related actions and you need to organize them by date or user.

Important concepts

Activity
An action recorded by the system.

User
The person who performed the action within the system.

Action type
Classification of the action performed. This may include actions such as create, edit, delete, or sent.

Date
Date and time when the recorded event occurred.

Expandable detail
Additional information that can be opened within a row to review more context.

Tabs
Separations within the screen that may organize activity by type or module, if the view allows it.

Log
A historical record that allows system actions to be reviewed.

What information the main screen shows

The main "Activity Feed" screen shows a list of recorded events.

Each event may include information such as:

• User who performed the action.
• Date and time of the event.
• Action type.
• Related module or record.
• Visible activity detail.
• Additional information available by expanding a row.

Depending on configuration and permissions, the screen may also include:

• Search.
• Date range filters.
• Tabs by activity type.
• Column sorting.
• Expandable rows with more detail.

This screen allows actions to be reviewed in an organized way without modifying the original data.

How to read the activity feed

To review an action, first look at the main data in the row.

Review:

• Who performed the action.
• When it happened.
• What type of action it was.
• Which record or process appears to be related.
• Whether additional detail is available.
• Whether the action belongs to the module you are investigating.

If the row has expandable detail, open it to get more context.

The feed helps understand what happened, but in some cases, it may be necessary to open the original module to confirm the current state of the record.

When you do not have an exact date, start with an approximate range and adjust the search based on the results.

Investigating an unexpected change

When someone reports that something changed without explanation, use the "Activity Feed" to reconstruct what happened.

Recommended steps:

1. Define which record, module, or process you want to review.
2. Identify the approximate date of the change.
3. Filter by the closest date range.
4. Search by user, client, job, or related keyword.
5. Review actions such as create, edit, delete, or sent.
6. Open the details of relevant events.
7. Compare the information found with the current record in the corresponding module.
8. If necessary, document the result of the review.

This process helps determine whether the change was made by a user, when it happened, and which action was recorded.

Using date filter

Date filters are useful for reducing the number of results.

Recommendations:

• Use a broad range if you do not know when the action occurred.
• Narrow the range once you find an approximate date.
• Review the day before or after if the change may have happened outside the expected time.
• Use smaller ranges when there are many similar actions.
• Confirm the event time if you need to reconstruct a sequence.

Filtering correctly prevents reviewing too many unnecessary records.

Using search

Search can help find activity related to visible data on the screen.

You can search by information such as:

• User name.
• Client name.
• Related job.
• Visible text in the record.
• Action type.
• Keyword related to the event.

If you do not find results, try clearing the search, expanding the dates, or using a different keyword.

Using tabs and sorting

If the screen includes tabs, use them to separate activity types or modules.

For example, there may be tabs to review general activity, jobs, or other event groups.

Column sorting can help you review:

• Most recent activity.
• Oldest activity.
• Actions by a specific user.
• Events grouped by action type.
• Related names or visible data.

When there are many similar actions, sorting by date or user can make the investigation easier.

Reviewing expandable details

Some rows may include additional information that appears when expanded.

Expandable detail can help you better understand:

• Which record was affected.
• What action was performed.
• What additional information is available.
• Which data may be useful for investigation.
• Whether the action corresponds to the case you are reviewing.

If the detail does not explain the full change, open the original module of the record to complete the investigation.

Difference between auditing and editing

The "Activity Feed" is an audit tool, not an editing tool.

From this module, you can review actions, but you should not expect to modify original records from here.

If you find data that needs to be corrected:

1. Identify the original module.
2. Open the corresponding record.
3. Make the correction if you have permission.
4. Save the change.
5. Use the activity feed again if you need to confirm that the action was recorded.

Best practices

To use the activity feed correctly:

• Always start with an approximate date.
• Use filters before reviewing long lists.
• Open expandable details when available.
• Compare the activity with the current record in its original module.
• Do not assume that one row explains all the context.
• Review nearby actions in time to understand the sequence.
• Sort by date when investigating recent changes.
• Sort by user when investigating actions by a specific person.
• Document important findings when necessary.
• Limit access to users with review responsibility.

Audit recommendations

When using the "Activity Feed" for an important review:

• First define what you are investigating.
• Keep the approximate event date.
• Review several nearby actions, not just one row.
• Compare the results with the current record.
• Avoid drawing conclusions without reviewing context.
• If the case is sensitive, share the finding only with authorized users.
• Document the review if it is part of an internal process.

Expected result

By the end, the user should be able to:

• Review actions recorded in the system.
• Search activity by date, user, or visible data.
• Use filters to reduce results.
• Open expandable details when available.
• Identify who performed an action.
• Understand when a change occurred.
• Investigate created, edited, deleted, or sent actions.
• Compare activity with the current record in the corresponding module.
• Use the "Activity Feed" as a consultation and audit tool within Diamond Operations Pro.