First Login
Used to confirm the EVE character and attach saved reports to that account. It does not read wallet, assets, skills, location, private mail, or corporation data.
Preview ConsentJSON Preview
WarpIntel asks for EVE permissions only when a feature needs them. Public tools work without login, and first sign-in should stay limited to public identity until private modules are enabled.
Used to confirm the EVE character and attach saved reports to that account. It does not read wallet, assets, skills, location, private mail, or corporation data.
EVE sign-in is feature-flagged off until the production callback is confirmed and a test sign-in succeeds.Preview ConsentJSON PreviewProduction callback to enter in the EVE Developer Portal:https://warpintel.app/api/auth/eve/callback
Public sign-in is hidden until the production callback is confirmed.
Client ID and secret are present in the runtime without exposing their values.
The runtime callback matches the public WarpIntel callback URL.
publicData is allowed for the first sign-in and account shell.
9 of 10 permission groups are fully allowed in the runtime scope list.
1/1 scope(s) allowed
5/5 scope(s) allowed
5/5 scope(s) allowed
9/9 scope(s) allowed
8/8 scope(s) allowed
1/1 scope(s) allowed
5/5 scope(s) allowed
15/15 scope(s) allowed
6/6 scope(s) allowed
2/8 scope(s) allowed; 6 still gated
Each feature keeps its own consent moment. Preview links show the exact scope bundle before any CCP redirect.
First sign-in only asks for publicData.
Dashboard shell, saved-report boundaries, account controls, and permission summaries are staged.Ask only when a signed-in pilot requests live skill, clone, implant, or fitting comparison.
Manual fitting review works now without EVE SSO.Ask when a user chooses authenticated audit evidence instead of pasted browser-local notes.
Local audit scoring and scope-gap summaries are available before private sync.Ask when a signed-in pilot wants private asset, order, wallet, contract, or job views.
Public market and appraisal tools work without account data.Ask only when a user wants authorized colony review rather than public template planning.
PI templates and planning helpers are public-data ready.Ask when a signed-in pilot opens SRP proof, fleet participation, or private killmail review.
Manual SRP intake is live and guarded without private EVE data.Ask after role review confirms the character can authorize corporation-level data.
Manual corp audit and corp stats tools work from pasted or public information.Ask only inside a human-triggered action flow with a confirmation step.
Fleet pages are advisory-first; write/client actions remain disabled for launch.Confirms the pilot signing in and lets WarpIntel attach saved reports to that EVE character.
Supports future contact, standing, watchlist, recruiting, diplomacy, and alert reviews after explicit opt-in.
Lets Fit Lab and the Skill Planner compare doctrines against live skills, queue, clones, and implants.
Adds private character activity, calendar, research, blueprint, title, medals, notification, FW, loyalty, and fatigue context for audit-style reviews.
Supports private order, wallet, contract, asset, industry, and mining views for the signed-in pilot.
Lets PI tools forecast colony layouts, production risk, and storage pressure after explicit opt-in.
Adds proof context for fleets, losses, location, ship type, online state, and private killmail review.
Enables authorized corporation dashboards for membership, structures, wallets, contracts, markets, jobs, mining, and killmails.
Supports corporation governance, hangar accountability, divisions, facilities, member titles, medals, FW context, and operational audit logs.
Covers future user-triggered actions like saving fittings, fleet controls, contacts, calendar responses, or client handoff.
The developer application may have a broad allowed-scope set for the mega-app roadmap, but the app should request only the scopes needed for the feature a user is turning on. Location, online state, wallet, corporation finance, and write/action scopes require extra care, visible explanations, and human confirmation. Scope requests can be checked through the safe consent preview before a user is redirected to CCP.
Shows the minimal public identity scope WarpIntel should use for first sign-in.
This preview does not start OAuth, contact CCP, or expose private EVE account data.Shows how WarpIntel explains a future write/action fleet scope before any CCP redirect.
Write/action scopes stay feature-specific, user-triggered, confirmation-gated, and human-reviewed.