Why connections matter
Meaningful work rarely lives inside one conversation. The source material may be in files, the evidence in a browser, the audience in a platform, and the final change in a connected service. A connection lets Dayric carry the objective across those boundaries.
Connections can provide context, enable an action, or both. Keep access intentional: each connection should have a clear purpose, an appropriate scope, and a boundary you understand.
Add a connection
Connect a tool when the active objective needs information or an action that only that service can provide. Dayric should make the account and requested access clear before the connection becomes available to the work.
- Open the connection request from the active work or your connected tools.
- Choose the intended service and confirm the correct account.
- Review what Dayric can read, create, update, or send.
- Complete authorization, then return to the objective and confirm how the connection should be used.
Set the working boundary
Access should match the work. Tell Dayric which source is authoritative, which areas are out of scope, and which actions must return to you before they happen.
- The account, workspace, folder, or property that belongs to the objective
- Whether the connection is for reading context, taking action, or both
- Information that should not be used or carried into the result
- External changes that require an explicit approval
Keep consequential actions visible
A connected tool extends Dayric's reach; it does not transfer your authority. Review the destination, content, scope, and reversibility of consequential actions before approving them.