You asked chat to change something and it's showing you a card.
In Rhodes: the chat panel
Chat asks before it changes your records. The exceptions are recalculations Rhodes can redo on its own, such as refreshing an entity's deadlines, and documents you attach, which Rhodes files the same way as any upload. When you ask for a change, it works out exactly what would happen, checks it, and shows you a card describing it in plain words.
Nothing is written until you click Approve on the card. Untick any line you don't want; Skip All declines the lot. Lines that send documents, change a provider or change your team start unticked: tick each one you want. Pending cards also wait on Home under Needs you. After you approve, each line shows Applied, Failed or Skipped. A failed line says why underneath it; if you've reloaded since, ask chat why instead. Click Approve again to retry just the failed lines. Lines already applied aren't applied again. If Approve itself doesn't get through, the card says "Something went wrong, and we couldn't confirm these changes were applied. Check your records, then try again if they're missing."
Team changes come on a card of their own, and so does each secure share. Deletions need an admin or owner. If a name matches more than one person or entity, chat asks which one you mean instead of guessing.
Only the person who asked for a change can approve it. In a chat shared with your team, changes a colleague asked for appear under Staged by a colleague: you can see them and their status, but not tick them, and they don't wait on your Home.
So asking for a change is safe — the worst case is a card you decline. Read the card rather than the request: it describes what will actually be done, which is the thing you're approving.