Use “Update a federated participant” in Recued. CAS-updates role, display label, task-assignee identity, contract binding, and active status for one participant.
Update a federated participant
Use “Update a federated participant” in Recued. CAS-updates role, display label, task-assignee identity, contract binding, and active status for one participant.
Complete workflow
Federated Projects
23 pinned recipes
Use Federated Projects in Recued for project management, federation, records, and work entity. It includes 46 actions and 14 ready-to-run workflows. Actions that change data use Recued's approval controls. It works on its own: one person can run every project here with nothing to connect. Add the people you work with by email, assign them work, and track effort. Install Federated Project Peer later, when someone you work with runs their own Recued.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Initialize a federated project” in Recued. Creates the authoritative project and atomically seeds federation policy, the owner participant, invitation evidence, and a four-state workflow.
Use “Federated project command board” in Recued. It provides a complete workspace with project and tasks plus participants, peers, workflow, effort tracking, dependencies across peers, filter controls, actions, and diagnostic details.
Use “My federated day” in Recued. Reads every federated project you own and returns the open work assigned to you — overdue first, then due today — with no peer, connection, or contract involved.
Use “Show a federated project” in Recued. Reads one project beside its pack-private federation record and peer inventory.
Use “Add a federated participant” in Recued. Records an accepted invitation and active Limited to the approved agreement participant in one Records batch.
Show all 23 recipes
Use “Register a federated peer” in Recued. Adds the local policy row that names a connected peer Source and its contract.
Use “Define a federated workflow state” in Recued. Adds one deterministic allowed task state for a project.
Use “Edit the federated workflow” in Recued. Loads the project workflow into an editable schema-derived grid and applies every submitted row atomically with Records CAS.
Use “Transition a federated task” in Recued. Validates the project-owned workflow vocabulary before changing native task state and progress.
Use “Log federated task effort” in Recued. Creates or CAS-updates the exact fixed-point effort row for one native task.
Use “Report federated project effort” in Recued. Aggregates exact estimates and actuals and shows the task-level rows behind the totals.
Use “Add a cross-node task dependency” in Recued. Stores the explicit string tuple that represents a dependency beyond the local reference namespace.
Use “Check cross-node dependencies” in Recued. Shows active remote pointers and the native tasks they can block; missing remote rows are never interpreted as deletion.
Use “Apply a peer's federated project update, then answer” in Recued. It carries out the named workflow using the connections and settings you choose. Changes remain behind Recued's approval controls.
Use “Peer: list one federated project” in Recued. Limited to the approved agreement peer list. It returns an array only after participant authorization.
Use “Peer: read a federated project” in Recued. Authorized peer read for exactly the configured project.
Use “Peer: update a federated project” in Recued. Limited to the approved agreement peer write for manager/owner/contributor roles.
Use “Peer: list federated tasks” in Recued. Limited to the approved agreement peer list for tasks under one authoritative project.
Use “Peer: my federated day” in Recued. It uses the connections and settings you choose when you run it.
Use “Peer: read a federated task” in Recued. Authorized peer read that verifies task parentage before rendering.
Use “Peer: update a federated task” in Recued. Limited to the approved agreement peer write that validates membership, task parentage, and optional workflow state before mutation.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Also where a participant who was seated by email alone gets their contract id, once they run their own Recued server. That one field is the whole handover: the participant row keeps its identity, so the work already assigned to them stays assigned and simply becomes readable from their side. Leave a field empty to keep what is there.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (12 steps)
participant_id
trim
Trim whitespace from setting participant id
participant_id_required
template
Generate text from a template
fail: step.participant_id is_empty
current
recued-core.federated-projects.participant.get
Get participant on federated projects
assigned_contact_input
trim
Trim whitespace from setting assigned contact id
assigned_contact_fallback
default
Apply default
assigned_contact_id
lowercase
Convert assigned contact fallback to lowercase
contract_input
trim
Trim whitespace from setting contract ref
reserved_owner_contract_guard
template
Generate text from a template
fail: step.contract_input equal user_self
reserved_public_contract_guard
template
Generate text from a template
fail: step.contract_input equal public_anonymous
contract_ref
default
Apply default
write
recued-core.federated-projects.participant.update
Update participant on federated projects
updated
recued-core.federated-projects.participant.get
Get participant on federated projects
▼
Output
record_fields
updated.record
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
role
setting
=
[object Object]
active
setting
=
true
contract ref
setting
=
[object Object]
display name
setting
=
[object Object]
participant id
setting
=
[object Object]
assigned contact id
setting
=
[object Object]
Uses (2 operations)
Pack operation
Get participant on federated projects
recued-core.federated-projects.participant.get
Pack operation
Update participant on federated projects
recued-core.federated-projects.participant.update
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Write
Pack
Federated Projects
external change
Read: participant.get · No approvalWrite: participant.update · No approval