Read and write access (future)

Short answer: StackTether has no write tools today; the AI cannot change anything in your systems. When write tools arrive, every one starts off for every user. An admin turns a write tool on per tool and per person, must type a fresh 2FA code to do it, and every change is logged. Keep your read-only API user; a separate read-write API user will be needed only for write tools.

How write tools will be controlled

• Off by default. No user, admin included, gets a write tool automatically.
• Per tool, per person. An admin switches on one tool for one member on that member's page (the Tools section, marked Coming soon today). "All on" for vendor access will never turn on write access.
• Fresh 2FA. Turning on any write access needs a new authenticator code at that moment, so a stolen signed-in browser alone cannot grant it.
• Logged. Every grant appears in the member's history, and every write call in the audit log. A write call records a "started" entry before anything changes.
• Tied to vendor access. Turning a connection off for a person, or any password or 2FA reset, also removes their write grants on it.
• Described exactly. Each write tool says what it changes and is marked as such to the AI app.

Why so strict

A wrong or tricked AI write can change client records, reassign tickets or log time in someone's name. Text inside a ticket can try to instruct an AI. Each grant must therefore be deliberate, per person and traceable.

How to prepare later (do not do this yet)

1. Keep the read-only API user exactly as it is. Read tools keep using it.
2. When StackTether announces a write tool, create a second, separate API user for writes, with add or edit rights only on the entities that tool changes (for example ticket notes), never delete.
3. Name it clearly (for example "StackTether Write") and give it its own monitored mailbox.
4. Turn the write tool on only for the people who need it, one by one.
5. Review the audit log for write calls weekly while you get used to it.

Risks of write access

• Mistakes at speed: an AI can make many changes quickly.
• Prompt injection: vendor text that looks like instructions.
• Attribution: changes appear under the API user in the vendor's history unless the vendor supports acting as a named resource.
• Wider blast radius if a credential leaks.

FAQ

When are write tools coming?

There is no date. Tell us which write action you need most through the contact form.

Can I turn on write access for my whole team at once?

No. By design it is per tool and per person.