All rights reserved
AWRA reserves its protected brand and product assets while making it clear when people may reference AWRA, share public materials, or request written approval for names, logos, screenshots, documents, product UI, diagrams, and brand references.
Last updated: June 6, 2026
AWRA reserves its rights in the AWRA OpsHub platform, website, documents, visuals, interfaces, names, logos, marks, code, workflows, product materials, and original content unless a written agreement says otherwise.
You may make truthful, non-misleading references to AWRA or AWRA OpsHub when describing compatibility, reviews, tutorials, procurement comparisons, customer use, or integrations.
Do not imply that AWRA sponsors, endorses, certifies, employs, funds, owns, or approves you, your product, your content, your event, or your organization unless we have given written permission.
If your use is commercial, prominent, promotional, co-branded, paid, sublicensed, redistributed, or could confuse people about ownership, ask AWRA before publishing.
What the footer means
All rights reserved means AWRA keeps ownership and control over its protected intellectual property except where AWRA grants rights through law, public guidance, an open license, a customer agreement, a partner agreement, or a separate written approval.
You can still talk about AWRA, link to public AWRA pages, cite AWRA as a tool you use, write reviews, make accurate integration references, and share public legal or trust resources for evaluation. The important line is confusion: people should not think your content, product, event, page, listing, certificate, training, marketplace item, or company is owned, approved, sponsored, or operated by AWRA unless that is true and written permission exists.
This guidance does not replace a signed agreement. If a customer order form, partner contract, reseller agreement, data processing agreement, procurement addendum, or brand approval gives different instructions, that written agreement controls for that relationship.
Protected assets
The list below is not exhaustive. It explains the kinds of assets that usually require careful handling, attribution, or permission depending on context.
AWRA, AWRA OpsHub, AwraIQ, AWRA Systems, AWRA Inventory, AWRA public page names, feature names, product names, slogans, release names, campaign names, and similar identifiers.
Official logos, lockups, symbols, icons, colors, badges, app icons, product marks, social avatars, trade dress, navigation identity, and visual combinations that identify AWRA.
Screens, dashboards, mobile views, vendor portal views, inventory, procurement, finance, sales, asset, automation, reporting, AI, billing, and admin interfaces.
Website copy, help docs, public guides, whitepapers, reports, blog posts, images, diagrams, product screenshots, demo videos, training material, downloads, and documentation.
Demo datasets, sample workflows, templates, reports, diagrams, pricing examples, benchmark notes, implementation checklists, and generated product outputs prepared by AWRA.
Application code, scripts, components, database structures, internal tools, APIs, mobile app logic, automation rules, design tokens, and proprietary implementation patterns.
Usually acceptable
These examples are allowed when they are accurate, non-confusing, respectful of customer privacy, and not prohibited by another agreement.
You may state that your organization uses AWRA OpsHub, is evaluating AWRA OpsHub, integrates with AWRA OpsHub, or has written about AWRA OpsHub, provided the statement is true and not misleading.
You may link to AWRA public pages, help articles, legal resources, trust resources, status pages, blog posts, and documentation as long as the link is not sold as a standalone asset or presented as your own content.
Customers and prospective customers may share AWRA public resources internally with procurement, IT, finance, legal, compliance, and implementation teams for evaluation or governance review.
You may create tutorials, walkthroughs, or training notes that accurately describe how AWRA works, as long as the material is clear that it is unofficial unless AWRA has approved it.
Developers may use the AWRA name in a diagram to show accurate interoperability, provided AWRA branding is less prominent than the developer or customer offering and no endorsement is implied.
Journalists, analysts, reviewers, and researchers may refer to AWRA for news, commentary, comparison, or criticism, subject to accuracy, fair dealing, fair use, and applicable law.
Do not do this
Do not suggest AWRA approval, certification, partnership, sponsorship, reseller authority, investor relationship, employment relationship, or customer endorsement without written permission.
Do not use AWRA names, logos, product screenshots, color systems, UI patterns, domain names, social handles, app names, or ad copy in a way that could make people think your offering is AWRA.
Do not register domains, app listings, social accounts, email addresses, ad keywords, repository names, or community pages that use AWRA marks in a confusing or official-looking way.
Do not distort, recolor, rotate, animate, add effects to, combine, crop, outline, place inside another shape, or use outdated AWRA logos unless brand guidelines or written permission allow it.
Do not copy AWRA screens, workflows, diagrams, product naming, website structure, help content, forms, emails, reports, or UI to create a confusingly similar product or service.
Do not sell, license, package, bundle, distribute, or monetize AWRA assets, screenshots, documents, templates, recordings, or training materials as standalone commercial assets.
Do not use AWRA marks or copyrighted works in malware, phishing, spam, deceptive ads, abusive content, illegal activity, adult content, hate content, harassment, or reputationally harmful material.
Do not scrape, bulk download, mirror, crawl at abusive scale, or use AWRA content to train, fine-tune, evaluate, or populate a competing product without permission.
Practical examples
Screenshots and product UI
AWRA may show inventory, procurement, assets, sales, POS, vendors, finance, approvals, audit logs, messages, attachments, billing, and AI insights. Treat every screenshot as if it could reveal business operations.
Screenshots should use your own workspace, an authorized demo account, synthetic sample data, or fully redacted information. Never expose another organization, vendor, employee, customer, student, supplier, payment, or personal record.
A screenshot must show real product behavior or a clearly labeled mock/demo environment. Do not edit screens to imply AWRA has features, certifications, approvals, pricing, or results that are not available.
Remove or obscure emails, phone numbers, addresses, tokens, barcodes, QR codes, payment references, invoices, purchase orders, IDs, audit logs, location data, API keys, and any confidential customer information.
Make it obvious whether the screenshot is from AWRA, your product, a customer environment, a tutorial, a review, an integration diagram, or a comparison.
If a screenshot includes third-party logos, documents, maps, images, vendor records, customer names, or plugin content, you are responsible for having permission to show them.
Do not use AWRA screenshots in phishing, fake login pages, fake billing notices, deceptive ads, credential harvesting, fake support pages, or impersonation workflows.
Relationship categories
The fact that someone uses, evaluates, integrates with, supplies, implements, comments on, or teaches AWRA does not automatically create brand rights.
Customers may identify AWRA as a vendor or tool they use when the statement is accurate. Public case studies, logos, quotes, press releases, procurement references, or testimonial use may require separate written approval.
Implementation partners, consultants, resellers, trainers, or advisors must follow their written agreements. Without written permission, do not claim official partner status, certification, reseller rights, or preferred provider status.
You may describe truthful compatibility and API or workflow interoperability. Your product name, logo, and listing must remain distinct from AWRA and must not look like an official AWRA module.
Supplying goods or services to AWRA does not create permission to use AWRA as a public endorsement. Vendor references, portfolio logos, and case studies need written approval.
Meetups, training sessions, webinars, and communities may mention AWRA as a topic, but names and promotion must make clear whether the event is independent or officially sponsored.
Use current facts, avoid implying endorsement, and contact AWRA when you need confirmation, quotes, product images, executive comments, or brand assets.
Attribution language
Attribution does not replace permission when permission is required, but it helps readers understand ownership and relationship boundaries.
AWRA OpsHub is a trademark or service mark of AWRA Systems or its applicable owner.
Certain AWRA materials, screenshots, diagrams, and documentation are copyright AWRA Systems. All rights reserved.
This material is independently produced and is not sponsored, endorsed, or approved by AWRA.
This integration is designed to work with AWRA OpsHub. AWRA has not endorsed this integration unless expressly stated in writing.
Permission requests
Email [email protected] before using AWRA assets in a way that is prominent, commercial, co-branded, public, paid, sublicensed, redistributed, partner-related, or likely to affect customer trust.
How we review
Does the use describe AWRA, the product, the relationship, and the technical behavior truthfully?
Is your own brand clearly more prominent than AWRA unless AWRA is the publisher?
Could a reasonable visitor think AWRA created, owns, sponsors, certifies, endorses, or operates the material?
Could the use expose customer data, support confusion, security risk, billing confusion, phishing risk, or operational harm?
Is the use part of paid ads, resale, training, marketplace listings, partner pages, or a public sales motion?
Is the use respectful, lawful, non-deceptive, and aligned with trusted enterprise operations?
Important limits
AWRA may update these guidelines to reflect product changes, new marks, new brand systems, legal developments, partner programs, or customer safety requirements. Continued use of AWRA assets should follow the current version of this page.
Nothing here grants ownership of AWRA intellectual property, waives AWRA rights, creates a partnership, creates a reseller relationship, creates an endorsement, or limits AWRA remedies where rights are misused.
Help Center
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.
