Company pages

Every organization on Sifa has a shared page at /c/<domain>. It starts as an auto-generated stub built from public company data, and the people who work there connect to it from their profiles.

When you list an employer, a university, or a certificate issuer on your profile, that organization has a home on Sifa ID too. It lives at /c/<domain>, keyed to the organization's own domain: Spryker's page is at https://sifa.id/c/spryker.com. One shared page per organization, so every person who links it points at the same place.

A company page is not a personal profile. A profile belongs to one person and holds their history, their activity, their endorsements. A company page belongs to the organization and holds public facts about it, plus the connections that people draw to it from their own profiles.

How a company page starts

Every company page begins as an unclaimed stub. Nobody creates it by hand. The first time someone links an organization from a profile entry, Sifa generates the page from public company data and starts serving it at /c/<domain>.

An unclaimed stub says so plainly. A note sits above the fold: "Sifa generated this page from public company data. [Company] has not verified it." The card carries an Unclaimed badge. Its dashed, muted styling shows that nobody from the organization stands behind it yet.

Sifa generates these pages, and nobody verifies them, so they stay out of search-engine indexes for now. They exist to give the links on your profile somewhere real to point, not to rank as company directory pages.

Where the data comes from

An unclaimed stub takes its facts from open, public company registries. It never takes them from text that a Sifa user typed. Sifa reads them from sources like Wikidata, GLEIF (the global legal-entity register), and ROR (the Research Organization Registry).

Depending on what those sources hold, a stub can show:

The organization's canonical name and website
Industry
Headquarters country
Year founded
Employee count
A short description
The logo

The page omits every field that the public sources do not cover. A stub with only a name and a domain is normal. More detail arrives as the source data improves.

One thing a company page does not show is a roster of who works there. Sifa deliberately holds back per-person headcounts and employee lists on these pages. The connection runs the other way: you decide, on your own profile, which organizations to link.

How your profile connects to a company page

You reach a company page through a link on your own profile. Attach the Company field of a work position to a match from the Sifa organization typeahead. That entry then points at the shared page. The same holds for the institution on an education entry, the issuer on a certificate, and the rest.

A link keeps the connection live, and plain text does not. When Sifa later corrects the name of the organization, the correction follows every link. Your profile then shows the current name, and you edit nothing.

Companies and organizations holds the full walkthrough. It covers a missing organization and a name correction.

Verifying a company with its domain

A company page uses the identity model of a person on Sifa: your domain is your username. A personal profile swaps alice.bsky.social for alice.com after it proves control of the domain. The proof is a DNS record or a .well-known file (see Use your own domain). An organization verifies itself the same way, through the domain that already keys the page.

That is why a company page lives at /c/<domain> and not at an arbitrary Sifa ID. An organization can prove that it controls the domain. That proof turns an unclaimed stub into a verified page that the organization runs.

Claiming and managing your page: coming soon

Today a company page is read-only. It is a generated stub, and nobody owns it yet. The next step gives an organization the page. That step exists as a design, and it is not live. When it ships, an organization verifies itself through its domain, corrects the public facts on its page, and controls how the page appears.

Until then, use the name-correction flow for the most visible field. Anybody who links the organization can suggest a corrected name. An approved correction updates the name on every link to that company.

Companies and organizations: link an organization on your profile to its shared page, add a missing one, and suggest a name correction.
Import from LinkedIn: imported positions arrive as plain text. Reopen each one and link it so the entry points at the real organization.
Use your own domain: the domain-as-username model under company verification.