Settings
Find the right settings page, change the name customers see, route payment alerts, and update your own profile.
Settings holds both organization-owned information and your personal Seev account details. Before changing anything, work out whether the change should affect the whole business workspace or only your own login, because switching organizations changes the first kind and never the second.
Find the right settings page
Settings groups everything under Workspace settings. Each page needs its own permission, so a page you cannot see is one your role does not grant rather than one that does not exist.
| Page | Belongs to | Needs |
|---|---|---|
| Business Identity | The active organization | organization.verification.manage |
| Business profile | The active organization | organization.verification.manage |
| Alerts | The active organization | organization.alerts.manage |
| Payouts | The active organization | payout_settings.read or payout_settings.manage |
| Personal profile | Your login | Nothing. Every member sees it. |
| Team permissions | The active organization | Any of team.read, team.manage, role.read, role.manage |
Owners and admins hold every permission. See Team Access for granting a member less than that.
Change the name customers see
Business Identity controls the name shown at checkout, on invoices, on payment links, on storefronts, on receipts, and in payment notifications. The page shows the verified legal name, the name currently shown to customers, the identity verification status, and the review status of any name change.
Enter a name between 2 and 120 characters. Anything shorter or longer is refused with "Business name must contain between 2 and 120 characters." and nothing is submitted. The field shows a live character count against the 120 limit.
A name change goes to review, not straight to your customers. The current name stays active on checkout and receipts until the new one is approved, and while a request is pending you cannot submit another. Get the name right before submitting rather than planning to correct it.
Replacing a name that was already approved asks you to confirm first, since it puts the approved name back into review. On submission you get "Your name-change request was submitted for review".
The review status reads Approved, Pending review, Changes required, or Not configured. Changes required means the request was rejected; read the reason on the page and submit a corrected name.
Read the business profile
Business profile shows the KYB or KYC details held for this organization, drawn from its verification record. It is where you confirm what Seev actually holds rather than what you believe you submitted.
Editing opens the verification flow with the existing information prefilled, so you update the existing record rather than starting a new verification type. If the verification was rejected, read the reason before changing anything. See Complete Verification.
Route payment alerts
Alerts controls where Seev Plus emails a notification when the organization receives a successful payment. Turn the successful-payment alert on, enter the address that should receive it, and save.
Saving with the alert enabled and no address shows "Enter an email address for payment alerts."; an address Seev cannot parse shows "Enter a valid email address." Neither submits anything. A failure at the server shows "Could not save alert settings" and leaves the previous setting in force, so check the toggle state after an error rather than assuming the change landed.
A teammate holding only read access to this page sees a "View only" badge and disabled controls rather than an error.
This alert address is not the address that receives the weekly transaction summary, which always goes to the organization owner. See Accounts and Wallets.
Set up payouts
Payouts controls how often settled funds move and where they go. Manual payouts are no longer offered, so an organization collecting money needs a schedule and a destination.
See Payout Schedules before you enable one.
Manage team access
Team permissions covers members, built-in roles, and custom roles built from permission keys. Give each person their own login and the least access that lets them work.
See Team Access.
Update your own profile
Personal profile changes your own account details, such as your name. These follow you between organizations and appear in greetings and account menus. They do not change any organization's verification record, and changing your personal name does not change the name customers see.
Settings also carries the appearance choice between light, dark, and system.
Turn on two-step sign-in
Two-step sign-in asks for a code as well as your password each time you sign in, so a stolen password is not enough to get into your account. It is off until you turn it on, and it applies to your own sign-in, not to everyone in the organization.
- Open Settings, then Personal profile.
- Under Two-step sign-in, choose Turn on.
- Pick where codes are sent: Email, which uses your account's address, or Text message, which uses a phone number you give.
- Enter the 6-digit code we send. This confirms you can read messages at that address or number.
From then on, signing in takes your password and then a code. A code lasts 10 minutes and stops working after five wrong tries; ask for a new one from the same screen.
To turn it off, choose Turn off and enter a code sent the usual way. We email you whenever two-step sign-in is turned on or off, so a change you did not make does not go unnoticed.
If you lose access to the phone or inbox your codes go to, you cannot sign in. Contact support@seevcash.com to recover the account.
If a change does not appear
Work through these before resubmitting anything.
- Confirm the active organization in the sidebar selector. A change saved in one organization will not show in another.
- Check whether the field is waiting on review rather than saved. A business name under review leaves the old name in place by design.
- Check whether verification is locking the field. Details submitted for review cannot be edited while the review is active.
- Reload once before assuming the save failed.
Repeated submissions of the same change do not speed up a review and can leave duplicate requests behind.