Manage team collaboration

Keep collaboration organized, accountable, and recoverable as more people start working in Stackby. Use comments and history for context, structure your views to reduce clutter, and set up backup habits so mistakes never become disasters.

Track updates with comments and record history

• Use comments on records to capture decisions, ask questions, and @mention teammates for quick follow-ups.

• Rely on revision history to see who changed what and when, restoring prior values if needed.

• Tip: Encourage “decision-in-the-record” habits—summarize outcomes in a comment so context travels with the work.

Add checklists, reminders and activities

• Add checklists or subtasks, setup reminders or add custom activities like call logs, meeting summary or notes on each record.

Keep your views in order with view sections

• Group related views into sections (e.g., Team, Planning, QA, Reporting) so teammates can find the right lens fast.

• Standardize naming: “PM: This week,” “Design: In progress,” “Leadership: Rollup.”

• Lock configurations for critical views to prevent accidental filter/sort changes.

Back up any stack with snapshots

• Take manual snapshots before large changes (schema updates, imports, permission rewires).

• Set a recurring admin rhythm (weekly or biweekly) to verify snapshot availability and retention.

• Keep a short runbook: when to snapshot, where to store notes, and how to roll back.

Restore important data from Recycle Bin

• If something is deleted (tables, views, fields, or records), restore it from Recycle Bin within the available retention window.

• For granular fixes, use record-level revision history to revert cell values without rolling back the entire table.

• After recovery, audit recent changes and tighten guardrails (field/table edit permissions) if needed.

Practical checklist:

• Comments capture key decisions; @mentions used for handoffs.

• Views named, sectioned, and locked where appropriate.

• Snapshot before big changes; confirm recovery steps.

• Trash and history policies known by admins; permissions reviewed quarterly.