What exactly does OBAM authorize?
OBAM authorizes specific public reference claims, such as logo display, testimonial language, and case-study mentions. Each claim is approved by the referenced company and tracked with a clear status.
FAQ
Frequently asked questions
Answers for legal, procurement, brand, and security teams evaluating OBAM.
Legal & IP
Who has authority to approve, expire, or revoke a reference?
Your organization defines who can approve or control references through role-based permissions. Legal, brand, and business owners can each be assigned scoped authority so control stays aligned to policy.
Can we revoke usage immediately if a relationship changes?
Yes. Authorized references can be revoked or expired as soon as relationship terms change. Verification status updates immediately so public trust signals match current reality.
How do we handle logos vs testimonials vs case-study text?
OBAM treats each asset type as a separate reference claim with its own conditions and lifecycle. You can allow a logo while restricting testimonial copy, or sunset case-study text on a different schedule.
Procurement
Does OBAM replace procurement due diligence?
No—OBAM is not a procurement scoring or risk-rating system. It adds an auditable authorization signal so procurement can validate whether a public reference is genuinely approved.
What verification signal does procurement actually see?
Teams see whether a claim is active, expired, or revoked, plus when that status was last updated. This gives buyers a concrete trust signal instead of relying on static logos or outdated decks.
Can buyers verify status without logging in?
Yes. Public verification pages can be shared so external buyers can confirm status without creating full product accounts. Internal users can still use authenticated workflows for deeper controls.
Brand/Partnerships
Can marketing teams still move fast with approvals?
Yes. Teams can use pre-set policy rules and scoped approvers to avoid long ad hoc review chains. This keeps campaigns moving while maintaining centralized control over reference usage.
How do we enforce policy conditions on logo usage?
Policy conditions are attached directly to the logo claim, including usage scope and timing. If conditions are no longer met, status can be changed to expired or revoked and reflected in verification surfaces.
Security & IT
What audit trail is captured?
OBAM records approval, policy updates, status changes, and user actions tied to each reference. Teams can review who changed what and when for internal governance.
How do roles/permissions work?
Access is role-based so teams can separate administrative control from day-to-day operations. You can assign least-privilege access across legal, procurement, brand, and security stakeholders.
Do you support enterprise controls (SSO/SCIM roadmap or plan-tier gating)?
Enterprise controls are supported based on plan and rollout scope, with SSO and lifecycle identity integrations managed as part of onboarding. We can align required controls with your phase and governance needs.
Commercial / rollout
Can we start with one team and expand later?
Absolutely. Many customers begin with a single control owner, then extend to procurement, brand, and security teams as process maturity grows.
How long does initial rollout take?
Initial rollout is typically measured in weeks, depending on policy complexity and stakeholder alignment. A focused first use case usually goes live fastest.
What determines pricing?
Pricing is based on deployment scope, control requirements, and enterprise features needed for your workflow. We structure plans so teams can start lean and scale as adoption expands.
Next step
Put reference control in place with the right owners first.
Best first step: align legal/IP owners, then expand to procurement and brand. We will map how you can authorize, govern, and revoke references with a clear verification signal.
Not ready for demo? Review pricing to self-qualify first.