1. Your Profile
Your profile is the page people see when they look you up. It shows your career stage, verified affiliations and ORCID iD, links to your work elsewhere, the groups you belong to, and everything you publish.
2. Career Stages
Pick the one that fits you. There are 15, listed roughly in career order, and yours shows next to your name:
| Career Stage / Role | Description |
|---|---|
| Student | Studying at undergraduate or masters level. |
| PhD Candidate | Working toward a doctorate. |
| Postdoctoral Researcher | Holding a doctorate and working on a fixed-term research appointment. |
| Research Staff / Technician | Supporting research as permanent staff — technicians, engineers, data and lab managers. |
| Lecturer / Teaching Faculty | Faculty whose appointment is primarily teaching. |
| Assistant Professor | Early-career faculty, typically pre-tenure. Equivalent to Lecturer in the UK. |
| Associate Professor | Mid-career faculty. Equivalent to Reader or Senior Lecturer in the UK. |
| Professor | Senior faculty, typically leading a research group. |
| Researcher | Doing research in a role none of the more specific titles above describes. |
| Industry Researcher | Working in research or development outside academia. |
| Clinician | Practising medicine or allied health, with or without a research role. |
| Science Communicator | Writing about, teaching or broadcasting science to a wider audience. |
| Enthusiast | Here out of curiosity rather than professionally. |
| Institution | An account representing an organisation rather than a person. |
| Funder | Funding research — a foundation, agency or individual donor. |
3. ORCID Verification
You connect an ORCID iD by signing in to ORCID itself. There is no text box for it, so nobody can attach an iD they do not control.
- Connect your ORCID iD by editing your public profile header.
- Sign in on ORCID’s own page and approve the connection.
- OWL stores the iD ORCID sends back (e.g.
0000-0002-1825-0097). - One account per iD: an ORCID iD can be linked to one OWL account only.
- Your profile shows a green ORCID badge that links to your ORCID record.
Researcher Identity
Cryptographic ORCID Integration
Optional, connected by signing in to ORCID
Official 3-Legged OAuth
0000-0002-1825-0097
What it gives you:
- Nobody can attach an iD they do not control
- Each iD can be linked to one account only
- Badge links to your ORCID record
Institutional Registry
Academic Affiliation Badges
Only domains confirmed in our institution registry count
What it gives you:
- Verified
.edu/.ac.ukaddress, confirmed by email - Turns into a past affiliation once its end date passes
- Webmail addresses never count
Account Security
Two-Factor Authentication
Optional; worth it if you run a group or its money
Authenticator Code
482 910
What it gives you:
- Works with any authenticator app, such as Google Authenticator or 1Password
- A code from your app is needed to sign in
- Recovery codes are stored hashed and shown only once
4. Institutional Email Verification
Display verified badges for your current and past academic appointments:
5. Current vs Past Affiliations
Every affiliation is in one of two states, and which one it is decides how it appears to everyone else. The state is not a switch you set independently; it is read from the end date, so it can never disagree with the dates shown next to it.
The tick means one specific thing: at some point you proved control of an address on that institution’s own domain. Leaving does not make that untrue, so the verification is kept and the badge simply changes tone.
- You do not need access to the old address to mark an affiliation as past.
- You do not need to re-verify if you later restore it to current.
- Deleting an affiliation is a different action: it removes the record entirely, and re-adding it means verifying by email again, which is impossible once you lose access to the address. If you have simply left, mark it past rather than deleting it.
| State | When it applies | How it appears on your profile |
|---|---|---|
| Current | No end date, or an end date that has not passed yet (a contract with a known finish date is still current until that day). | Emerald badge reading Verified Affiliation. Listed first. |
| Past | An end date that has already passed. | Muted slate badge reading Verified Past Affiliation, with the end date in the tooltip. |
How to mark an affiliation as past
- 1 Go to Settings > Affiliations. Affiliations are grouped under Current and Past headings.
- 2 On the affiliation you have left, click I’ve left.
- 3 Confirm the last day you were there. It defaults to today, so if you have just left you can accept it as-is.
- 4 Click Mark as past. The affiliation moves to the Past section immediately, and the badge on your profile changes tone.
6. Profile Customization & External Links
The top of your profile can show:
- Avatar: a square image (up to 1MB, automatically optimized to WebP).
- Cover banner: a 4:1 image (1920×480px, up to 2MB), such as a lab photo or a figure from your work.
- Research interests: up to 8 research areas, as broad or specific as you like (e.g. Physics / Quantum / Optics). People browsing those areas can find you.
You can paste either a full URL (e.g. https://github.com/torvalds) or a plain handle (e.g. torvalds). OWL keeps only the part that identifies you and builds the link from that.
Dr. Jane Doe
Associate Professor of Quantum OpticsConnected Academic & Social Links:
Code & Model Hubs
GitHub · GitLab · Hugging Face · Kaggle
Share research datasets, open weights & software repos
Citations & Registries
Scholar · arXiv · Semantic · PubMed · OSF · Zenodo · DBLP
Author pages on citation indexes and preprint servers
Social & Discussion
Bluesky · Mastodon · Discord · YouTube · LinkedIn · X · Reddit
Direct public scientific communication and outreach links
Code & Data Repositories
Repositories, models and datasets:
GitHub: Handle or full profile URL
GitLab: Handle or full profile URL
Hugging Face: Organization/user handle or model link
Kaggle: Profile handle or dataset page
Academic & Citation Indices
Where your publications are indexed:
Google Scholar: 12-character user ID or citations URL
arXiv: Author identifier (e.g. smith_j_1) or profile URL
Semantic Scholar & PubMed: Author ID or bibliography URL
Open Science Framework (OSF) & Zenodo: Project/DOI IDs
OpenReview & ResearchGate: Profile handle or vanity URL
DBLP: Computer science bibliography handle
Social & Community Channels
Where people can follow you:
Bluesky & Mastodon: Handle or instance account
LinkedIn & Threads: Profile URL or public slug
X (Twitter): Handle or profile link
Discord & YouTube: Server invite or channel handle
Reddit & Telegram: Subreddit, username, or channel
7. Sparks vs Articles
You can publish two kinds of post:
Sparks (Micro-Posts)
Short posts of up to 1,024 characters, with up to 20 images or videos and an optional poll. Use them for early results, conference notes, quick questions or paper announcements. Sparks are not filed under research areas.
Articles (Long-Form)
Long pieces with headings, LaTeX maths, syntax-highlighted code, tables, and images with numbered figure captions. Articles are filed under research areas.
8. Notifications & Preferences
Notifications come in five categories, each set separately in Settings > Notifications:
- Social: likes, bookmarks, reposts and quotes, replies, new followers, badges, group invitations and group link requests.
- Chat: direct messages and your groups’ chat rooms under Messages.
- Fundraising: review decisions on your campaigns, new contributions, a campaign reaching its goal, and updates from campaigns you backed.
- System: platform announcements and moderation notices.
- Security: sign-ins from a new device, password changes and email changes. These cannot be turned off.
9. Security & Two-Factor Authentication (TOTP)
Two-factor sign-in is optional, and worth turning on if you run a group or its fundraising:
10. Recovery Codes
Recovery codes are how you get back into your account when your authenticator app is gone (like a lost, wiped, or replaced phone). Enabling 2FA takes you straight to the recovery codes page, where one click issues a set of 10 single-use codes, each looking like ABCDEFGH-IJKLMNOP.
A set rather than one code, because a single code cannot actually be spent: using it would leave the account with no way back in at all. With a set, each lockout costs one code and the remaining count is shown in your settings long before it reaches zero.
- Single use: A code stops working the moment it signs you in. 10 codes means 10 recoveries before you need a new set.
- Shown exactly once: They are stored hashed, the same way passwords are, so nobody, including our team, can display them again. Copy or download them when they appear.
- Counted, not listed: Settings > Security (2FA) shows how many of the 10 remain, and warns you when three or fewer are left.
- Regenerating replaces the set: Generating new codes invalidates every code you currently hold, including unused ones. Regeneration asks for a code from your authenticator first.
Accounts enrolled under the older scheme hold a single recovery code. It still works, once. Settings > Security (2FA) flags this, and generating a new set replaces it with the full 10.
How to sign in with a recovery code
- 1 Sign in with your email and password as usual.
- 2 On the two-factor screen, click Lost your device? Use a recovery code.
- 3 Type any unused code. Hyphens, spaces, and lower case are all fine: only the letters and digits are compared.
- 4 You land on the recovery codes page, which tells you how many are left and lets you generate a new set.
How to generate a new set
- 1 Go to Settings > Security (2FA) and click Manage recovery codes.
- 2 Enter the current 6-digit code from your authenticator app.
- 3 Click Generate new codes and save the 10 codes shown.
11. Developer API Keys
API keys let your own scripts use the Content API, for example to publish posts:
- Key Format:
owl_sk_<id>_<secret>. - Shown once: the secret is displayed when you create the key and stored only as a SHA-256 hash, so it cannot be shown again.
- Endpoints: Authorized developers can create, list, and revoke programmatic keys via
/api/v1/keysor request developer access via our Contact Form.
