You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Design: where and how should admins edit their workspace tax ID #94911
We have to start collecting the tax-id of the business when a customer has a non-USD workspace that enables travel. We need to figure out how this should look to users, and how we ask for it.
Open Design Questions
Where does the admin go to edit their tax ID?
Should the current tax ID be shown in full, partially masked, or hidden (edit-only)?
changed the title [-]Tax ID cannot be edited after travel is enabled on a non-USD workspace[/-][+]Design: where and how should admins edit their workspace travel tax ID after initial submission[/+]on Jun 29, 2026
changed the title [-]Design: where and how should admins edit their workspace travel tax ID after initial submission[/-][+]Design: where and how should admins edit their workspace tax ID[/+]on Jun 29, 2026
Would this only show for people with travel enabled as it's a bit weird without context on why we need it? Also, I take it we'd limit it to be seen by the admins/auditors that view this page? (as we do other fields in Overview as it's a tab also accessible by regular members).
If so, I don't think we need to mask it - but I'm basing that off my understanding of what this ID actually is here locally in the UK. The equivalent of the TIN in the UK is the CRN (Company Registered Number), which is publicly accessible on Companies House. For example, you can see Expensify Limited's here.
I guess my other question is whether we really need to be able to edit it? Just thinking like in the VBA set up flow we capture a TIN in KYC, but we don't offer an option to edit it in product. I don't even know how you legally, or would need to, change it.
The mocks looks good, and if we do want to display it/allow admins to edit it, I like the placement on the overview page.
Tom raises some questions above that sound totally valid to me, but alas I know nothing about this so I don't know that I can meaningful contribute to that part of the discussion 😂
Activity
[-]Tax ID cannot be edited after travel is enabled on a non-USD workspace[/-][+]Design: where and how should admins edit their workspace travel tax ID after initial submission[/+]melvin-bot commentedon Jun 29, 2026
Triggered auto assignment to @shawnborton (
Design), see these Stack Overflow questions for more details.[-]Design: where and how should admins edit their workspace travel tax ID after initial submission[/-][+]Design: where and how should admins edit their workspace tax ID[/+]samranahm commentedon Jun 29, 2026
Following.
shawnborton commentedon Jun 30, 2026
Do we ever mask Tax IDs? Like in any of the VBA flows, would we do that?
I like your idea of putting it below the company address in overview:
cc @dannymcclain @Expensify/product for a quick gut check on that
trjExpensify commentedon Jun 30, 2026
Would this only show for people with travel enabled as it's a bit weird without context on why we need it? Also, I take it we'd limit it to be seen by the admins/auditors that view this page? (as we do other fields in Overview as it's a tab also accessible by regular members).
If so, I don't think we need to mask it - but I'm basing that off my understanding of what this ID actually is here locally in the UK. The equivalent of the TIN in the UK is the CRN (Company Registered Number), which is publicly accessible on Companies House. For example, you can see Expensify Limited's here.
I guess my other question is whether we really need to be able to edit it? Just thinking like in the VBA set up flow we capture a TIN in KYC, but we don't offer an option to edit it in product. I don't even know how you legally, or would need to, change it.
dannymcclain commentedon Jun 30, 2026
The mocks looks good, and if we do want to display it/allow admins to edit it, I like the placement on the overview page.
Tom raises some questions above that sound totally valid to me, but alas I know nothing about this so I don't know that I can meaningful contribute to that part of the discussion 😂
shawnborton commentedon Jun 30, 2026
Agree, great points Tom! I'm also not sure how to answer them, so I will let you all sort it out :)
blimpich commentedon Jul 2, 2026
Alright I think we've sorted this out here, closing this design issue