Best Of

I would like to be able to say add a record a date action after a change a cell value. For instance, I would like to change the cell value to the person being escalated to and then record the date that the escalation takes place in an escalation date column.

When I choose to change the cell value first, then there is no option to record a date. If I choose to record a date first, then I don't have the option to change a cell value.

I created a separate automation for the record a date, but to me it would have been simpler to have been able to include it in the escalation automation.

If this is already a possibility, please let me know.

Thanks

Freda

Smartsheet is very useful for collecting data through forms from non-users and organizing it in a database, from which automations can be run.

The "generate document" automation is one I use particularly frequently. It's very helpful in making "receipts" of the most crucial information for other parties to review in a format they can easily review, while having other data stored usefully in the data sheet.

Right now, other parties like administrators/leadership, don't want to utilize smartsheet unless absolutely necessary. Use of the software is mostly relegated to us support staff. When reports are too much information or too tedious, a generated document works.

Right now there's no way to integrate the attachment files generated through automations and put them into google drives. Through data-shuttle, one can export spreadsheet data from smartsheet to google drive, indicating an understanding that there's a need for smartsheet data to be available elsewhere. It would be incredibly helpful if there could be a function that would allow me to automatically export auto-generated attachments to assigned google folders.

I am submitting a request to modernise the Bulk User Import/Export functionality. Currently, the BulkImportTemplate and the User.csv export provide only a fraction of the data required for effective enterprise user management, leading to significant manual overhead for System Administrators.

1. The "BulkImportTemplate" Limitation
The current template is restricted to: First Name, Last Name, Email, Seat Type, Group Admin, Resource Viewer, and Sys Admin.

To manage an organisation at scale, we need this template to support additional fields. My recommendation is to update the template to include optional fields for:

• Department
• Job Title/Role
• Company
• Group Membership (e.g., adding users to existing Contact Groups during the import process)

Proposed Mandatory vs. Optional Standards:

• Always Mandatory: First Name, Last Name, Email.
• Optional but Supported: All other profile metadata and permission toggles.

2. The "User.csv" Reporting Gap
The corresponding reporting function is equally limited. The current User.csv output includes basic status and roles but excludes the very metadata we need for auditing and resource planning.

Current Fields: Name, Email, Status, Sys Admin, Group Admin, Licensed User, Resource Viewer, Sheets (Owned), Last Login, Time Added, Trial Status.

Requested Update:
The User.csv export should be updated to include Department, Title, and Group Affiliations. Without these, Admins are forced to manually click through individual user profiles to verify if users are correctly categorised or assigned to the right functional teams.

The Business Impact:
For any organisation with more than 100 users, "Bulk" management should mean more than just adding an email address. It should allow for the complete setup of a user’s professional profile. Enhancing these templates would turn a multi-hour manual audit into a 5-minute CSV task.