ActivityLog follows design reviews and versions from Figma and creative-seat changes from Adobe, tied to clients and to the delivery that followed.
Comments, approved versions and the hand-off to the client in order.
Janet's part of the review on the Ana Trujillo data warehouse designs: her Figma comments, the version labelled 'Final - approved' on Wednesday at 08:45, then her invite of the client's guest to their SharePoint site at 11:30. Figma supplies the review; SharePoint supplies the hand-off. Comments from others on the same file show on the team view.
Janet Leverling's Figma files with the versions she saved and comments she made. Edits Figma sends without a person are counted for the file, not for her.
Design activity by client and deliverable, and which creative seats are not being used.
Versions, comments and library publishes per client deliverable this week, from Figma. Only activity Figma attributes to a person is credited to them; unattributed edits count for the file only.
Adobe Creative Cloud seats by person, with seat changes over the quarter. Andrew's seat shows no design work or Adobe sign-in for over 60 days. Adobe gives no usage data, so this is marked as an inference, not a last-used date. Figma activity per designer is shown separately.
Design activity comes from Figma's notifications about versions, comments and library updates, and from Adobe's admin history of who holds a seat. Client hand-offs come from SharePoint sharing.
Named versions saved, comments, library publishes and file deletions, with the file name and the designer.
Figma sends these to a web address you create in ActivityLog. On the Professional plan Figma names people by their Figma handle, which we match to your staff with a short list.
Admin changes: users added or removed and licences assigned or removed, with who made the change.
From the Adobe Admin Console's admin history.
Files shared with clients and guests invited to client sites, with time and person. Never the file content.
The read-only Microsoft 365 connection, approved once by your Microsoft 365 admin. It reads Microsoft's own audit trail.
Figma reports versions, comments and library publishes. Adobe reports seat changes. SharePoint reports the hand-off to the client.
Figma handles are matched to people from a short list you keep. Files are tied to a client by a rule on the file or project name, for example 'Ana Trujillo - Data warehouse'.
Design activity by client and deliverable, each review cycle from first comment to client delivery, and creative seats with their last design activity.
Designers show their review cycle end to end. The delivery lead sees effort per client and reclaims seats nobody uses.
Not precisely. Figma does not say who made everyday edits, only who saved versions and left comments. Design effort is shown from those moments, so treat it as effort you can see, not hours worked.
No. We record file names, version labels and that a comment was made, with who and when. We do not download files, images or comment text.
By a rule you set on the file or project name, so a file named 'Ana Trujillo - Data warehouse' lands on the Ana Trujillo client.
ActivityLog is in beta. Connect the tools you already use and get this report for your organisation.
See pricing →Questions first? Talk to us → · All use cases
