Who controls your team's digital business cards?
Scaanme lets a company manage employee digital business cards, review changes before publication and switch a departing employee's public card off. Teams working in Arabic and English can use these controls to keep published work details consistent and manage collected leads. Directory-driven onboarding and Microsoft Entra ID single sign-on are separate requirements: do not assume that central card management includes them.
Most card administration happens after employees start sharing their profiles. A representative changes their number, a department changes its name, and someone leaves with a printed NFC card still in their desk. Your pilot should cover those events before you buy hardware for everyone.
What the company should own
| Item | Practical rule |
|---|---|
| Public profile | The company decides which work details appear |
| Employee access | Give each person the appropriate account access; avoid a shared password |
| Brand approval | Test locked fields and the review process with an ordinary employee account |
| Lead records | Confirm which manager can see and export each team's enquiries |
| Departure | Handle employee access and public card availability as separate checks |
Scaanme's team controls include card activation and deactivation, a review mode and a view of team leads with CSV export. Brand field locks exist at organization and individual-card level. Ask for the exact configuration to be demonstrated on your account before treating it as part of your rollout.
A pilot that exposes the awkward cases
Start with a manager and a few employees from different departments. Give one person a long Arabic name, another an English job title, and another both a direct number and a switchboard number. Open the profiles on different phones rather than approving screenshots alone.
Try an ordinary edit, then a restricted one. The employee should be able to correct an allowed detail without changing a field reserved for the company. In review mode, verify what the public sees while an edit is waiting for approval, and who receives the work of approving it.
Mixed Arabic and English text deserves its own check. A telephone number can look plausible while its punctuation appears on the wrong side. The W3C's explanation of bidirectional text describes why mixed writing directions need care. For acceptance, read the number aloud from the actual card and compare it with the source record.
Work out how people join
Ask the administrator to demonstrate both a new employee and a person who already has an account. These are different cases. An existing account must not become company-controlled solely because somebody typed its email address into a form.
Scaanme's current team administration prevents that automatic takeover. Plan the account setup with support when an employee already uses the service, and avoid promising an invitation workflow until it has been demonstrated for your account.
For a large workforce, also measure the time spent setting up each person. A small pilot can hide repetitive work that becomes significant at hundreds of accounts. Keep one approved source file for names and work details, record who checked it, and decide who maintains it after launch.
Test what happens when an employee leaves
Choose a test employee and record every public URL, printed QR code and NFC card assigned to them. Suspend the employee's team access as appropriate, then separately deactivate the public card. Open the old link in a private browser session and scan the physical card again.
An NFC card stores a destination. Taking an account action does not physically erase that chip. You need to verify the destination's behavior, and retrieve or reassign company hardware under your own process.
A saved contact on somebody else's phone is another copy. Updating or disabling a web profile does not silently rewrite every address book that previously downloaded its details. Explain that difference to managers so a successful offboarding check does not become a promise to erase every historical copy.
Compare administration with identity automation
If your policy requires directory provisioning, put that requirement on a separate line. Microsoft explains automated provisioning as creating and maintaining users in connected applications. A manager editing a card manually is a different process.
Ask vendors to show the applicable plan, identity integration and a real deprovisioning test. Scaanme's manual team controls may fit a department that prioritizes bilingual profiles; a mandatory SSO or automated HR workflow needs separate evidence before purchase.
Start with the digital business card product and the current pricing page. Request a written scope for the team account so the number of public cards, employee logins and any onboarding work are clear.
FAQ
Can one manager switch off an employee's Scaanme card? Team administration includes a public card toggle. Test the old URL after deactivation and handle the employee's account access separately.
Does a brand lock mean every employee shares a password? No. Brand control concerns what employees can change. Shared credentials make accountability harder and should not be the operating model.
Will an old NFC card stop opening the employee profile? It still opens its encoded destination. The result depends on that destination's current state, so scan the card after deactivation rather than assuming it is inactive.
Is central management the same as Entra ID SSO? No. One controls cards and team activity; the other concerns authentication through an identity provider. Confirm each independently.
