Plants — Transactions
Overview
Plants is a two-part module for managing physical plant locations and the collaborator access authorizations tied to them. The Plants tab maintains the master registry of locations; the Access tab tracks which collaborators are authorized to work at each plant, along with expiration dates and supporting documents.
For the record lifecycle and status transitions, see: Workflow.
Note
For common UI patterns used across SARA (tables, filters, dynamic columns, naming conventions), see: Common Features
Plants
Overview
The Plants tab is the master catalog of customer and client plant locations. Each record stores address data and an optional Google Maps link for quick navigation.
What you will see
- A paginated, filterable table of all plant records with status badges and location fields (name, country, state, city, address, zip code).
- A Map column that displays a blue location-pin icon for plants with a stored map URL; plants without a URL show
–. - ACTV and INAC status filter checkboxes at the top of the table for filtering the list by status.
- A Custom columns selector that controls which location fields are shown in the table.
Statuses and recorded changes
For status meanings and visual behavior across SARA, see: Status
For how changes are recorded, see: Logs & History
What you can do here
-
Create a new plant — Use the + New Plant button. Required fields are name, country, state, and city; address, zip code, and map URL are optional. The record is immediately active.
-
View a plant — Opens a read-only modal showing the plant's full address data.
-
Edit a plant — Opens the full plant form to update any field, including the Google Maps URL.
-
Deactivate / Activate — Toggle the plant between active and inactive states. Both transitions require confirmation.
Warning
Deactivating or activating a plant takes effect immediately after confirmation. There is no undo.
Access
Overview
The Access tab manages collaborator-level access authorizations per plant. Each access record links one collaborator to one plant, sets an expiration date, and can hold any number of supporting documents (such as permits or authorization letters).
What you will see
- A table of all access records showing the plant name, collaborator, days remaining until expiration, and expiration date.
- The Days left column displays a countdown in days; when the expiration date has passed, it shows Expired in red.
- The Access column shows a Download button for records that have attached documents; records with no documents show
–. - Status badges (ACTV / INAC) on each row. There are no status filter checkboxes on this tab.
Note
The status badge in both tabs uses a split button: the badge itself is display-only; the chevron (▾) opens the row action menu.
What you can do here
-
Create a new access record — Use the + New access button. Required fields are plant, collaborator, and expiration date. Files can be attached at creation time via the drag-and-drop upload zone. The record is immediately active.
-
View an access record — Opens a read-only modal showing the plant, collaborator, expiration date, and a list of attached documents with individual download links.
-
Edit an access record — Opens the edit form to update the collaborator or expiration date, add new files via drag-and-drop, or delete individual existing files. The plant assignment is fixed after creation and cannot be changed.
-
Download all documents — The Download button in the Access column downloads all files attached to that access record as a bundle, without opening the detail modal.
Info
Access records are automatically set to inactive when their expiration date is reached. See Workflow for the full expiration lifecycle and notification behavior.
Connections to other modules
- Collaborators — The collaborator field in access forms pulls from the SARA people directory, including external collaborators (prefixed with
[EXT]). - Plants → Access — The plant field in New Access pulls from the active plants list in the Plants tab.
Permissions
Permissions
Access and actions are permission-driven. See: Permissions