Organisation settings and API access

The settings dialog covers your organisation rather than any one student: your details, your licence and batches, your language, and API credentials. Open it from the profile row at the bottom of the sidebar and choose Settings.

My Organization and Subscription

My Organization shows the Organization Name, the Abbreviation used as the sub-domain in your organisation URL, the Organization URL itself, and your Account Manager's name and email. None of it can be typed over, and the panel says as much. That includes the abbreviation, since changing it would change the address your students use.

Subscription is where you check what you bought and how much is left. Current License and License Expires On describe the organisation's agreement, and the licence is what gates analytics and resume downloads. The Batches table lists each batch with its Plan, its seats as a remaining-of-total count, and its start and end dates. Add Ons shows extras marked Active, or reads No active add-ons.

Rename batch is the one thing in the dialog you can edit. It changes the label in the switcher and nothing else, so name a batch after the programme and intake year. Language sets the language the portal is shown in.

Extending a batch, buying seats and changing the licence all go through your account manager. Watch the batch end dates as well as License Expires On: they can differ, and students under a batch drop to Starter the day its period ends.

API Access

API Access manages the keys your own systems use to talk to FirstResume. Until your organisation is granted access the panel reads No API access yet with "Your organization hasn't been granted API access. Contact your account manager to enable it."

With access enabled you get an Integration Guide link to hand to whoever does the work, and Available APIs listing each rate limit as requests per minute.

1. Under Client credentials, press Create credential.
2. Give it a Credential name that says where it will run, for example "Production server".
3. Copy the key from the Copy your API key panel and store it where your team can find it.

The warning there is literal: "This key is shown only once. Store it somewhere safe. You won't be able to see it again." Close the panel without copying and the key is gone for good. Your way back is a new credential, or Rotate on the existing one, which issues a fresh key and shows that once as well. Revoke switches a credential off with no way back, and breaks whatever is still using it.

Tips

• Name each credential after the system holding it, so you know what breaks when you revoke it.
• Rename batches before term starts. The switcher and your exports both read better for it.
• Nothing in this dialog changes seats, dates or tiers.