Skip to main content

​
IX. Digital Ecosystem

​
1. the ibbe ecosystem

  • ibbe.in: this is our central home where we share our standards for modern education.
  • ibbe.in/apparatus: we share the same professional tools here that we use to build and grow our own team.
  • ibbe.in/compliance: we provide clear details here to ensure our operations remain honest and transparent.
  • ibbe.in/privacy: this space explains how we respect and protect your personal information.
  • ibbe.in/events: you can find all our upcoming gatherings and educational experiences here.
  • ibbe.in/newsroom: we post our latest stories and official updates for the community here.
  • ibbe.in/leadership: meet the mentors who guide our vision and set our global standards.
  • ibbe.art: we celebrate the history and soul of human creativity from every part of the world.
  • ibbe.blog: this is a quiet space for long-form thoughts on learning and practice.
  • ibbe.cloud: this is our private cloud infrastructure; it functions as a backend layer and does not serve as a public-facing portal.
  • jobs.ibbe.in: we invite talented individuals to join us in making education better.
  • jobs.ibbe.in/stories: we share the lived experiences and daily journeys of our team members here.
  • links.ibbe.in: find a simple path to all our social spaces and external resources.
  • certs.ibbe.in: this is where we issue certificates of employees with a link for veritifcation for public.
  • design.ibbe.services: this portal holds the visual elements that keep our brand clean and consistent.
  • docs.ibbe.services: we provide our internal team with the knowledge they need to succeed here.

​
2. official email identities

om@ibbe.in: this is the office of our co-founder, om rajguru. anzilah@ibbe.in: this is the office of our co-founder and lead for communications, anzilah dhalait. central@ibbe.in: this is our primary support channel where employees can reach our team or the ecu by using simple subject prefixes. email.ibbe.in: we operate our official mail domain through amazon ses to ensure all our communications stay reliable and clear.

​
3. Data Access Policy

IBBE follows a strict, role-based access model:
  • Officers only see what they’re working on
  • Managers distribute data on a need-to-know basis
  • Downloads of internal files are restricted unless flagged as “External Share Approved”
  • No IBBE doc should be circulated outside our ecosystem without watermark and approval
Breaches are logged, and misuse leads to immediate revocation of role and access keys → see conduct policy for more

​
4. Onboarding & Training Automation

IBBE’s onboarding system is being upgraded to run via docs.ibbe.in, with:
  • Auto-assigned learning tracks based on officer role
  • Built-in progress trackers and milestone reviews
  • AI-powered assistant that answers, “Can I do this?” based on our policy logic
  • Managers can upload new rolekits and assign mini-certifications inside the system
Goal: New members shouldn’t ask what to do. The system should show them.