A shipping line’s organisation on SCMTR.io

This page is for a shipping line's Indian agency — the company that files the line's SAM, SDM and their amendments (SAA, SDA) under its own PAN — and for the people who work with it. It explains how the line's whole team works in one place: head office, port branches, people who only need to look, and separate companies that handle the line at a port.

Who is at the top of a line's organisation?

The line's Indian agency: the company whose PAN files the line's manifests in India. One organisation on SCMTR.io is one agency and one line. An agency that acts for two lines keeps two organisations, one for each, so each line's manifests, people and settings stay apart.

What does "verified shipping line" mean, and how do we get it?

SCMTR.io staff check, once and by hand, that an organisation really is a line's Indian agency, and which line it is. Write to support@scmtr.io from your company e-mail; we confirm it with you and set it up. A verified organisation shows a tick beside its name — "Verified by SCMTR.io as <line>'s organisation in India" — and can:

publish its CSN cut-offs on the cut-off board from inside the app (the e-mail route to lines@scmtr.io still works as before);receive forwarders' change requests for manifests filed under its verified PAN — from their CSN amendments and from its own share links;invite sub-agents by the PAN they file under;let people from its company e-mail domains ask to join — an admin still approves each one;be suggested to its own staff when they open one of the line's manifests somewhere else.

To change the line, the verified PAN or the company domains later, write to support@scmtr.io from your company e-mail — staff change them, as they set them. Changing the PAN in your own filing profile does not move any of this.

An organisation that is not verified works exactly as before; nothing is taken away.

How do people join our line's organisation?

Always by an admin's decision. There are three ways in:

An invitation — an admin invites the person's e-mail address on Settings → Team, as for any organisation.A request from a company address — someone who signs in with one of your verified company domains sees "Your company <organisation> is on SCMTR.io — ask to join", under the header and on their Invitations page.A request from a file — someone who opens one of your line's manifests while signed in elsewhere sees "Work for <line>? Ask to join". This is only a suggestion to them: a PAN written in a file is never treated as proof that its uploader belongs to you.

Requests arrive on Settings → Team, and every admin is told. An admin approves — choosing whether the person can edit or only view (it starts at View only) and their branch — or declines. Approving sends the person an invitation, which they accept on their Invitations page; if they already belong to another organisation, that page asks what should happen to it, exactly as for any invitation. Nobody is ever added by their e-mail address or a file alone.

Can we set up our port branches?

Yes. On Settings → Team an admin adds branches — for example "Chennai" with its ports, "Nhava Sheva" with its — and puts each person in one. A branch is for organising your team: each person's My VCNs and saved SAM / SDM list open on My branch's ports (one press shows All ports; a search always covers every port), and change requests for a port are sent to that branch's people.

Everyone in the line can still read every port. An amendment at one port often needs the line's whole record of the vessel, so a branch never hides another branch's work.

Can someone only look, without changing anything?

Yes — make them a Viewer ("View only" on Settings → Team). A Viewer sees everything your organisation holds: vessel calls, SAMs and SDMs, SAAs, customs' replies, the count of what customs holds, and change requests. They cannot edit, save, request or approve changes, or send anything to ICEGATE. A band on every page says "View only", and anything they try to change answers: "You can view <organisation>'s work but not change it — ask an admin to make you an editor." Useful for managers, the principal line's staff, auditors and trainees. An admin sets Can edit or View only for each person on Settings → Team, and when inviting.

An admin is always an editor.

A separate company handles our line at one port. Can they work with us here?

Yes — as a sub-agent. On Settings → Filing agents, an admin chooses Invite a sub-agent and types the sub-agent company's PAN. The sub-agent's admins see the invitation — with your organisation's name — on their Clients page and accept or decline it; until they accept, you see only the PAN you typed.

When they accept, you see the accepting company's name and confirm it: Yes, it is our sub-agent, or Not ours. Nothing of yours reaches it before you confirm — the invitation found the company by the PAN its organisation gives, so the name is your check that it is the company you meant. Not ours ends the invitation, and the company is told. Once you confirm:

the sub-agent's admin chooses which of their people work for your line;those people see everything of your line, the same as your own staff, and work inside your organisation;your filings stay yours — the sub-agent's people act on your behalf, and the record shows the sub-agent's name;either side can end it at any time, and access stops at once — you on Settings → Filing agents, the sub-agent on its Clients page.

A sub-agent keeps its own organisation for its own work and its other principals. When you invite it you also choose whose ICEGATE ID the files its people prepare carry — yours (offered first) or its own. For your SAAs keep yours: customs ties an amendment to the SAM's submitter and type, and an amendment sent from another company's ICEGATE ID has not been seen accepted. You can change it later on Settings → Filing agents.

Who can publish our CSN cut-offs from inside the app?

In a verified line organisation: every admin, and any member an admin ticks Can publish cut-offs for on Settings → Team (never a Viewer, and never a sub-agent's people). They publish from Settings → Line → Publish cut-offs, using the same form as the line's desk link; every publication is recorded with who made it. A cut-off published this way appears on the board under your line, exactly like one you e-mail to lines@scmtr.io.

Who may file our SAA? Only the person who filed the SAM?

Customs ties an amendment to the company that filed the SAM — its PAN and its type (shipping agent or carrier), not to the person. ICES Advisory 37/2026 says "Who can file: Submitter of SAM", and customs refuses an amendment whose submitter does not match with error 230 ("Entity/Submitter MisMatch For Amendment Message"). The one 230 on file had the right PAN but the wrong type (carrier, where customs held the SAM as filed by an agent) — and it was sent from an ICEGATE user ID that files as a carrier. So use the type the SAM was filed under, and send from an ICEGATE user ID registered under that type (an agent's ID for an agent's SAM).

So on SCMTR.io anyone in your organisation who may edit can prepare the SAA, and whoever may send for your organisation sends it (if your admins turned on "only signers send", only signers). Each person signs with the DSC of the ICEGATE user ID they send from, as always — the person and the DSC have not been seen compared with the SAM's.

SCMTR.io checks the identity for you before anything is sent:

the submitter type differs from what customs holds for the SAM — error, with a one-press fix (Use ASA or Use ASC; this is error 230). It is a warning instead when customs' current record of the manifest cannot be confirmed, and it is read only from customs' record of this vessel call;the submitter PAN differs from the SAM's — warning (customs' rule says only the SAM's submitter may amend; no refusal for it has been seen yet);the file's submitter PAN is not one your organisation files under — warning before sending.

The authorised person and the DSC an amendment comes from are not checked against the SAM, because customs has not been seen to compare them. Which ICEGATE user ID sends it is not checked either — but send from one registered under the SAM's type, as above.

What happens to organisations that already file under our PAN?

Nothing changes for them. If more than one organisation on SCMTR.io already works with your line's files, each keeps its own work; nothing is merged or moved.

Where do we see all this?

Settings → Line (in a verified line organisation) shows which line you are, when you were verified, your company domains, your branches, your sub-agents, how many viewers you have, and the link to publish cut-offs. Settings → Team is where people, branches, viewers and join requests are managed.