SAVVYAdmin

SAVVY Admin

Delete Group

Delete and its assignments. Users can belong to multiple Groups: people with another Group keep those memberships.

Users who would have only the baseline Members Group afterward can be assigned to the destination you choose. Only current qualifying members are moved; pending or ineligible assignments are removed.

Mapped roles and ACL grants follow synchronization settings. Discord channels and Wanderer maps are kept. Disabled synchronization or manual grants may leave access in place.

Delete organization

This permanently deletes and its Groups, memberships, reports, invitations and service settings. Personal accounts, linked characters and other organizations remain.

Discord roles, server membership and Wanderer ACL grants remain in those services. Remove unwanted grants there before deleting the organization.

README
Audit history and Discord retries

Audit history is an owner-only disclosure at the bottom of Settings. It records actual Discord role/nickname changes and failure/recovery transitions, not unchanged automatic checks. Current synchronization status shows last checked and the next retry for failures. Persistent Discord permission/membership errors back off at 1, 2, 4 and up to 6 hours independently for roles and nicknames; transient failures keep the ten-minute reconciliation interval. Manual retry and relevant setting, identity, desired-role or main-name changes bypass the delay. Users without a linked Discord account remain excluded. Guest access removal retains its existing reconciliation path. Existing audit history is preserved.

Savvy Admin v1.33

Key features

Corporation management and personal tools for EVE Online.

  • Find assets across linked characters: Search every authorized linked character, including named ships and items inside ships or containers.
  • Vet reports: Vet combines employment, skills, contacts, mail and financial relationships across a user’s registered characters, with concerns highlighted in red.
  • Organizations and Groups: Invite Guests, review and admit Members, and use Groups for both Admin permissions and service access.
  • Connect Discord: Map Groups to server roles and use designated main-character names as server nicknames.

How to use

Sign in with EVE, designate your main, and link each character across your accounts. Personal and organization tools share one view. Your organization opens automatically; tasks follow your Group permissions.

TaskUse it to
HomeManage linked characters and browse the organization roster where permitted.
DashboardPersonal wallet/SP totals, saved PI attention, Online Players and ESI request-time history.
AssetsSearch linked inventories; organization searches require inventory permission.
WalletWallet journal and market transactions with wallet-style filters. Your characters load automatically; Owners and Managers can select an organization character or a user’s linked characters.
ContractsBrowse contracts with character, date, amount and text filters. Organization views require Owner or Manager access.
SkillsSkillpoints, learned skills and queues. Owners and Managers can select an organization user. Character lists start collapsed and show up to nine rows before scrolling.
PIPersonal colony/facility overview and extractor attention alerts.
InviteInvitation links and admission into Members. Requires Invite permission.
VetReports across a selected main’s linked characters. Requires Vet permission.
GroupsMembership, Admin permissions and service mappings. Owners define Groups and appoint staff.
SettingsPersonal alerts, timezone and character/data controls. Preferences save automatically.
ConfigOrganization setup and Discord/Wanderer connections; Owners only.
Characters, access and sharing

Sign-in verifies individual characters. Link every character you want included; no account assignment is needed. Admin cannot discover undisclosed characters or verify which EVE accounts you own.

Anyone signed in can create an organization or join through an invitation, regardless of corporation or alliance. A user and all linked characters can belong to one organization, including while awaiting admission.

Authorized inventories are automatically available to Owners and Groups with inventory permission in each organization you join, including characters linked later. Owners and Groups with the corresponding data permissions can investigate wallets/contracts, read Vet reports and authorized mail, or view organization character Activity.

Guests see only their own characters and personal tools; pending organizations, Groups, rosters and service details are hidden. Assigning Members, Veterans, Seniors or Leaders admits them. Groups control roster and Vet access. The Invite permission allows admission into Members; only Owners appoint staff or define Groups.

Every user designates a main. Any signed-in user can look up a registered character’s main, including across linked accounts. Removing stored personal data access stops further collection and shared access; downloaded report copies remain with their recipients.

Inventory results

Assets searches character inventories only. Your linked characters load by default; choosing another character set loads its saved inventories automatically. Collection follows all ESI asset pages for every authorized linked character. Search filters the full collected inventory; the table displays up to 500 rows at once. Narrow the search to see results beyond that display limit. Packaged ships may share a row: quantity 9 means nine ships.

Matching contents appear beneath their ship or container without unrelated contents. The Main column identifies the owner’s designated main. Column headings sort within that hierarchy; the arrow shows the active direction.

Collection runs hourly and respects ESI cache expiry, so recent movements may take time to appear. Observation times show snapshot age. A missing result does not establish that an item is absent. Station and authorized structure names identify locations even when the system name is unavailable. Structure lookups require structure read consent and the character’s access to that structure; reauthorize existing characters to add this consent. Lookups are cached per character. Some locations remain unavailable; Admin does not infer a location from its ID. Corporate hangars are not collected.

Vet and financial reports

Select a main to review every linked character. Only show guests starts checked; uncheck it to include all organization mains. The report shows character summaries, a combined employment timeline, contacts and standings, financial counterparties, source availability and collection times. Print/save PDF or download a standalone HTML report.

Mail checks cover sender and typed recipient IDs in up to 500 recent headers per character. Review-list matches are highlighted; corporation/alliance recipients can be broadcasts, and mailing-list IDs are not treated as character or corporation matches. Older mail, mailing-list membership and body text are not automatically scanned. Open Read mail to inspect a message as plain text; embedded content is not run.

Red concerns prompt a human review. Checks include organization review-list matches, recent character creation, frequent corporation changes and large external direct player transfers. Ordinary market transactions, fees and bounties remain financial context rather than wallet concerns. Contacts and past employment do not establish cooperation or allegiance.

Missing authorization is shown separately from concerns. No spy score or automatic admission/access restriction is generated. Use the links in the report to explore captured inventory, wallet, contract, contact, skill, employment and mail records. Source views keep the report’s collection time; mail bodies are retrieved on demand. These links require current Vet permission, including links in downloaded reports. Review the evidence before using Accept as member.

Vet covers every linked character, with up to 20 pages/10,000 records per endpoint per character.

ESI history is limited. Relationship summaries show up to 500 contacts and 100 financial counterparties, prioritizing review-list matches. Additional omissions and source limits are disclosed.

Wallet, Contracts and collection coverage

Use Entry type in Wallet Journal to select bounty prizes or another journal category. Filter records by character, local date range, credit/debit and absolute ISK amount. Transactions supports buy/sell, personal/corporation trades and searches by item, counterparty or location.

Refresh controls show the last and next user batch. All authorized characters for a user are queued together per subset, with users and subsets staggered. Records retain their actual observation times; partial batches are identified.

Wallet and Contracts show your linked characters by default and return saved records immediately. Owners and Managers can select an organization character or another user’s linked characters. Wallet and Contracts collect in separate hourly user batches, staggered relative to each other and other subsets, even while logged out. Refresh now respects ESI cache expiry; timers show the last and next poll. Failed endpoints retain previous records and observation times while retries back off.

Wallet Journal, Transactions and Contracts start collapsed. Expand either section to browse, filter or sort the records. Wallet and Contracts include all selected authorized characters and up to 20 pages/10,000 records per endpoint per character; each table displays 300 matching records per page. Filters and column sorting apply to all collected records before pagination. Transaction history is cursor-paged up to 10,000 records; older trades may be unavailable. Wallet inflow and outflow summarize available journal entries, not profit or net worth.

ESI history and authorization limit coverage. Collection times show snapshot age; updates follow ESI cache expiry and may not reflect recent in-game changes. Missing records do not establish inactivity.

Personal alerts

Character mute lists and Skills character overviews start collapsed and show up to nine rows before scrolling. The test DM is a separate action at the bottom of Alerts and does not enable any alert preference. Timezone has its own Settings section and saves after a completed change.

Settings → Alerts contains personal skill-training, Improved-implant travel and PI Discord preferences. Preferences save automatically; quick checkbox changes stay quiet, slow requests show progress, and failures remain visible with Retry. These controls are available without organization management permissions. Skills and PI keep their status and warnings; Skills shows the training alert count. Training-clone travel alerts appear in the Dashboard feed, where they can be dismissed.

Improved-implant travel alerts start disabled. Implant read consent is included in the full authorization set; enable these alerts in Settings. Every observed system change with any one of Cybernetic Subprocessor, Memory Augmentation, Neural Boost, Ocular Filter or Social Adaptation Chip in its Improved variant produces an Admin warning. Other implants, changes within the same system and the initial location baseline do not alert. Discord DMs are optional.

With travel alerts enabled, online characters are checked for location changes every five seconds while Admin is open or closed. Online status is refreshed about once a minute, subject to ESI cache expiry; logging into EVE may therefore take longer to detect. Location checks respect their own ESI cache deadlines. Implant snapshots use the separate five-minute batch schedule and are reused until their ESI cache expires; the implant batch is separate from the Skills display. Requests have bounded concurrency and errors back off for a minute. Each detected system change is a separate event; unchanged locations do not repeat it. Dismiss travel warnings in the Dashboard alert feed. Implant/location errors and long observation gaps reset the baseline. Events are encrypted and retained for up to 30 days.

ESI provides sampled location and current implants, not the implant set at the exact moment of travel. Trips between polls can be missed. This feature requests esi-clones.read_implants.v1 only when authorized; it uses existing location consent and does not require clone names or account identification.

Skills and training alerts

Skills defaults to your linked characters. Owners and Managers can select another organization user and see all their linked characters. Click a character’s name or expand its outline to inspect the training queue and learned skills, including category, trained level and active level. Tables are sortable and filterable; the character skillpoint chart is ordered highest first. Alert controls always remain personal in Settings → Alerts. Collection runs every five minutes while signed in or out; refresh respects ESI cache expiry.

Monitoring starts enabled, but a character must be observed actively training before an interruption can alert. A sustained pause creates one Admin alert after the grace period (15 minutes by default). Training must resume before another interruption can alert. This also handles expired MCT without repeated reminders. State persists across restarts; unavailable or stale data does not establish inactivity. Initial inactive characters remain unarmed.

In Settings → Alerts, use the master switch for training alerts and check Muted to suppress individual characters. Turning the master off preserves these character mute choices. Discord DMs are opt-in and require a linked Discord identity; delivery failures retry after 30 minutes. ESI cannot establish account membership, subscription status or available MCT slots. Completed queue entries are omitted. No new EVE scopes are required beyond the existing skill and skill-queue read permissions.

Dashboard and PI

Dashboard covers your linked characters and loads saved data automatically, refreshing in the background. Wallet balances are rounded down to whole ISK for display; source amounts retain their precision. Wallet/SP totals are snapshots and PI attention uses saved colonies. Online Players shows the latest count in its chart header. Charts show collected samples without backfilled history.

PI loads automatically and continues collecting while you are signed out. Last batch and Next batch show one PI collection schedule for all your authorized characters. Refresh colonies checks for available updates; ESI cache expiry still applies.

Extractor alerts use observed program end times. Ended programs appear red in the colony table. Colony contents and production may be stale until viewed in EVE; alerts may not reflect recent changes. Opt-in Discord DMs can notify you while Admin is closed.

Groups and Discord access

In Settings, Members see Join Discord only after admission to an organization with a configured server. Adding a user to Members admits them and applies that Group’s service mappings. Managers and Owners can admit Members; Owners alone appoint staff. Server nicknames follow mains by default.

In Config, an Owner signs in with Discord, adds the bot and saves the server ID. You need Manage Server permission or server ownership. The bot needs Create Invite, Manage Roles and Manage Nicknames, and must sit above the roles and members it manages.

Veterans, Seniors and Leaders have the same Admin permissions as Members, with independent Discord and Wanderer mappings. Groups grant both Admin permissions and external access. Use the user × Group checkbox table to admit Members, appoint Managers and inspect membership. Groups appear as a collapsed outline; expand one to see its users. Check a Group to add membership; uncheck it to remove membership. Changes save automatically; users can belong to multiple Groups. Automatic and inherited memberships are read-only. Only Owners control Config, edit Group definitions or assign staff. Custom Groups grant selected task permissions. Corporation/alliance filters use linked characters, and approval does not bypass eligibility. All conditions in a compound rule must match one character.

Role synchronization changes mapped roles only and retries automatically every ten minutes when enabled. Stale affiliation data holds dependent role changes. Discord hierarchy restrictions and other roles/channel overrides can still affect access; check synchronization status.

Wanderer setup and access

An Owner creates a dedicated access list in hosted Wanderer (wanderer.ltd), enables its ACL API key, and attaches that list to the maps it should grant access to. In Config → Wanderer, save the ACL UUID and API key. Use the ACL key, not a map token. Keys are encrypted and never returned to the browser.

Create Groups with eligibility and optional officer approval; a Discord role is optional. In Groups, define each Group’s Wanderer access as Viewer (read-only) or Member (full map access). Access applies to all linked characters of qualifying organization users; Member takes precedence. Guests receive no grants through this connector. Owners manage connections and Group definitions; the service synchronization permission allows previews and synchronization.

Preview changes before enabling synchronization. When enabled, Admin applies membership changes and retries every ten minutes. It removes only grants it previously created. Existing entries and manually changed roles are preserved; stale affiliation data holds dependent changes. Keep this ACL dedicated to Admin: Wanderer does not provide atomic conflict protection against simultaneous manual edits.

Other access lists, corporation or alliance grants can still provide map access. This connector does not guarantee immediate eviction from an active session. Wanderer administrative roles remain manual, self-hosted instances are not supported yet, and vetting concerns never trigger automatic access changes. No additional EVE scopes are required.

Deleting Groups and organizations

Owners can delete custom Groups from their membership panel or Define a Group. Select a destination and preview which users would otherwise have only Members. Those users remain in Members or receive the selected eligible assigned Group; other memberships are kept. Pending or ineligible source assignments are removed. Default Groups are protected. Type the Group name and review the access changes before deleting.

In Config, an Owner can delete the current organization after typing its name and acknowledging the external access notice. This removes its Groups, memberships, reports, invitations and service settings. Personal accounts, characters and other organizations remain. Existing Discord roles/server membership and Wanderer ACL grants remain in those services. Active reports or synchronization must finish first.

Permissions and availability

Fleet editing is itemized separately in Group permissions: Edit/delete fittings, Edit/delete doctrines and Edit master roles. Owners have all rights; Managers receive these by default, and other Groups can be granted each right independently.

Admin requests read access to assets, wallets, contracts, contacts, skills/training, mail, location, current ship and online status. Mail read access is included; mail sending, other write scopes and corporation scopes are excluded. Existing characters can reauthorize in Settings to restore the full scope set without losing other tools. Current-ship/online permissions do not provide historical movement tracking.

Corporate inventories, contract item details, historical movement/ship tracking and investigation alerts are not available yet.

Sources

Character data comes from CCP ESI; name suggestions also use zKillboard.

Admin is an independent project, unaffiliated with CCP Games or zKillboard. EVE Online artwork, trademarks and game data belong to CCP Games and remain subject to its Developer License Agreement.