Tasks, Events & Activities in REDA
Whenever you need to log a to-do, schedule a meeting or a viewing, or record that a call happened, you're working with activities — Tasks, Events, and logged calls. They're how REDA records what's been done and what's coming up against a contact, an account, an inquiry, a deal, or a property. This article shows how to create each, the difference between them, the standard Task statuses and priorities REDA uses, and the one REDA-specific point that catches people out: several REDA features create their own scheduled events, so you don't always add them by hand. Where those activities show up — the calendar and the record timeline — is covered in The Calendar & Activity Timeline.
Access you'll need. Tasks and Events are standard Salesforce objects, so access is granted separately by your administrator — it is not part of the REDA permission sets. If you can't edit a task, that's an org-side permission, not a REDA setting.
What activities are
Tasks, Events, and logged calls make up the standard activity layer REDA uses unchanged. A Task is a to-do with a due date. An Event is a calendar entry with a start and end time. A logged call is a record that a conversation happened. All three attach to the record you create them from and appear on that record's timeline, so the whole team shares the same history.
The choice between them comes down to time. If the thing has a deadline but no fixed hour — "chase the signed lease by Friday" — it's a Task. If it happens at a specific time — "viewing at 3pm Thursday" — it's an Event. And if it has already happened and you just want it on the record — "spoke to the tenant about the deposit" — it's a logged call. Getting this right keeps your Home page and calendar honest: due tasks surface as to-dos, events block time, and logged calls fill in the history.
One more thing to know up front: activities are visible to anyone with access to the record they're attached to. That's the point — the team works from one shared trail rather than private notes — but it also means a task or event you link to a deal is part of that deal's record, not a personal reminder only you can see.
Creating a Task
Create a task from the global + (New Task) or from a record's Activity composer (New Task) — creating it from a record links it to that record automatically. Fill in:
Mark a task complete when it's done — that sets its Status to Completed and moves it into the record's history.
Task Status and Priority
| Field | Values |
|---|---|
| Status | Not Started · In Progress · Completed · Waiting on someone else · Deferred |
| Priority | High · Normal · Low |
Creating an Event
Create an event from a record's Activity composer (New Event), the global +, or by clicking a slot in the calendar (which pre-fills the date and time — see The Calendar & Activity Timeline). An event carries a Start and End time and optional invitees. Two options are worth knowing:
Add Contacts or REDA users as invitees. As with tasks, Name links the primary person and Related To links the deal, account, or property. External attendees need to exist as Contacts first. For example, to pencil in a viewing you're arranging yourself, create a New Event "Viewing — Meridian Court #101", set the start and end time, add the tenant contact (say Aisha Rahman) as an invitee, and relate it to the property or the inquiry so it lands on that record's timeline. (A showing booked through REDA's showings feature already creates its own event — see the section below — so use New Event only for ad-hoc viewings you set up by hand.)
Logging a call
Log a Call records a completed activity, with a description, straight into the record's Activity History — no due date, no calendar slot. Fill in a Subject (for example "Called about deposit refund") and a Comments note capturing what was said, and it lands on the timeline stamped with the date and your name. Use it right after a phone conversation to leave a note the team can see. You can also add a follow-up Task from the same panel — handy when a call ends with "I'll send that over tomorrow."
REDA scheduled events vs. manual events
This is the REDA-specific point to remember. Several REDA features create their own Events automatically, which then appear on the calendar alongside anything you add by hand:
The takeaway: use New Event for ad-hoc meetings and viewings you schedule yourself; the items created by bookings, showings, and work orders don't need a manual event — they're already on the calendar.
Reference: Task vs Event
| Task | Event | |
|---|---|---|
| Time model | Due Date only | Start + End time (or All Day) |
| Typical use | Follow-up call, document reminder, renewal prompt | Property viewing, tenant meeting, inspection, team call |
| Completion | Mark complete → Status = Completed | Passes into history after it occurs |
| Reminder | — | Optional reminder |
| Links | Name (person) + Related To (record) | Invitees + Name + Related To |
Worked example: working David's lease
A leasing agent working Meridian's David Okafor lease finishes a viewing and opens David's contact to Log a Call recording the discussion. They add a New Task — "Send tenancy agreement for signing", Due Date tomorrow, Priority High, Related To the lease — which shows on David's and the deal's Activity area and in Today's Tasks on Home. They then schedule a follow-up with a New Event — "Lease signing — Meridian Court #101", next week, invitee David. The booked viewing itself was created earlier by the showings feature, not by hand — which is why it never needed a manual New Event.
Where to go next
- The Calendar & Activity Timeline — where tasks and events surface.
- Sending Email from REDA — sending and logging email as an activity.
- Scheduling Showings — a REDA feature that creates scheduled events.
- The Maintenance Calendar — scheduled work orders on the calendar.
- Council Events — the REDA record that shares the word "event".
Frequently asked questions
A Task has a Due Date and no time; an Event has a start and end time (or is all-day). Use Tasks for to-dos and Events for scheduled meetings and viewings.
Task editing is granted org-side, and no REDA permission set includes it. Ask your administrator to enable task editing on your permissions.
Not Started, In Progress, Completed, Waiting on someone else, and Deferred. Marking a task complete sets it to Completed.
Property showings, bookings, and work orders are created by those REDA features, not by New Event. Open the Showing, Booking, or Work Order record to manage the scheduled item.
You see your own by default. Seeing others' tasks requires org-side permission from your administrator.
On the record's Activity timeline and, if scheduled, on the calendar and the Home widgets — see The Calendar & Activity Timeline.
Was this article helpful?