An internal portal can feel private because it is limited to people inside the organization.
That does not mean every type of information belongs there.
BrightWeb is a company environment. Messages, documents, comments, screenshots, and shared links should be handled with the same care employees would use in any other professional setting.
The fact that a page is internal does not remove concerns about privacy, accuracy, confidentiality, or respectful communication.
A careless post can expose sensitive information, confuse coworkers, damage trust, or create a record that remains visible long after the original situation has passed.
Acceptable use begins with understanding that BrightWeb is a workplace resource—not a private chat, personal storage space, or public social network.
Internal Does Not Mean Open to Everyone
Employees may assume that information is safe to post because only Bright Horizons personnel can view the portal.
However, different internal audiences may still have different responsibilities and permissions.
A message appropriate for a center leader may not be appropriate for every teacher, administrator, or employee across the organization.
Before sharing information, consider:
- Who actually needs to see it?
- Does the audience need the full detail?
- Is there a smaller group that should receive it?
- Does the information belong in a formal reporting system instead?
- Could the post reveal something private about another person?
A company-only environment still requires audience control.
Avoid Sharing Personal Information About Children
Information about children should be handled with particular care.
Employees should not casually post details such as:
- Full names
- Medical information
- Behavioral concerns
- Family situations
- Photographs
- Incident details
- Attendance information
- Developmental observations
- Contact information
A legitimate workplace need may require certain information to be documented or communicated.
That does not mean BrightWeb is automatically the correct place for it.
Sensitive child information should follow the approved reporting and recordkeeping process.
The safest rule is to share only what is necessary, only with the people who require it, and only through the correct channel.
Family Information Should Remain Private
Employees may learn personal details about families through their work.
That information should not become casual internal discussion.
Avoid posting:
- Family disputes
- Financial concerns
- Medical situations
- Custody details
- Personal complaints
- Home addresses
- Private phone numbers
- Comments about parenting decisions
- Information shared in confidence
Even when a family situation affects center operations, the discussion should remain factual and limited to what employees need in order to perform their responsibilities.
Personal curiosity is not a professional reason to share information.
Protect Coworker Privacy
Employees also deserve privacy.
BrightWeb should not be used to publish personal details about coworkers without a valid business reason.
That includes:
- Medical conditions
- Leave information
- Performance concerns
- Disciplinary matters
- Personal contact details
- Family circumstances
- Private conversations
- Salary information
- Schedule disputes
- Complaints that have not been formally reviewed
A coworker’s absence may need to be communicated.
The reason for that absence may not.
A message such as “Jordan will not be in today” may be sufficient. Additional personal explanation may be unnecessary and inappropriate.
Do Not Post Performance Criticism Publicly
BrightWeb is not the place to publicly evaluate a coworker’s performance.
Messages such as these can cause unnecessary harm:
- “She never completes anything correctly.”
- “He is always late.”
- “This team cannot follow basic instructions.”
- “Everyone knows who caused the problem.”
Performance concerns should be handled through the proper management process.
Public criticism can embarrass the employee, create conflict, and make the issue harder to resolve.
Operational updates should focus on the task, not on humiliating the person involved.
Avoid Emotional Posting
Workplace frustration is normal.
Posting while angry is risky.
An employee who feels ignored, blamed, or overwhelmed may want to respond immediately. Written messages created in that state often sound harsher than intended.
Before posting, pause and ask:
- Am I describing facts or expressing anger?
- Does this need to be discussed privately?
- Would I use the same words in a meeting?
- Am I trying to solve the issue or punish someone?
- Could this message damage a professional relationship?
- Would I be comfortable if leadership reviewed it later?
A delayed, measured response is usually more useful than an immediate emotional one.
BrightWeb Is Not a Place for Personal Disputes
Personal disagreements between coworkers should not become company-wide content.
Avoid using BrightWeb to:
- Continue an argument
- Recruit others to take sides
- Publish private messages
- Criticize someone’s personality
- Respond sarcastically
- Retell a conflict in a public forum
- Demand an apology in front of others
A professional disagreement may need manager involvement, mediation, or a direct private conversation.
Posting it broadly usually increases the number of people involved without improving the outcome.
Do Not Share Rumors
Rumors can become more believable when they appear on an internal company platform.
Employees should avoid posting unconfirmed statements about:
- Staffing changes
- Center closures
- Leadership departures
- Policy changes
- Schedule changes
- Organizational restructuring
- Employee discipline
- Compensation decisions
- New company requirements
If the information has not been officially confirmed, it should not be presented as fact.
A statement such as “I heard this may happen” can still create unnecessary concern.
When uncertainty exists, employees should verify the information before sharing it.
Check Dates Before Reposting Information
Old internal messages can create new confusion.
A BrightWeb post may have been accurate when published but no longer reflect current conditions.
Before forwarding or referencing an older announcement, check:
- Original publication date
- Effective date
- Whether an update replaced it
- Whether the program has ended
- Whether the message applied only to one location
- Whether the deadline has passed
- Whether the linked document is still current
A screenshot of an old message does not prove that the information still applies.
The current internal source should take priority.
Screenshots Need Extra Care
Screenshots are convenient because they capture exactly what appears on a screen.
They can also expose information that was not intended to be shared.
A screenshot may accidentally include:
- Employee names
- Email addresses
- Internal navigation
- Private messages
- Child or family information
- Other browser tabs
- Notification previews
- Document titles
- Confidential company content
Before attaching a screenshot, review the entire image.
Cropping the intended section may reduce unnecessary exposure, but it does not make every screenshot appropriate.
Employees should also avoid sending internal screenshots outside the organization unless there is an approved reason and process.
Internal Links Should Stay Internal
A BrightWeb link may only work for authorized users.
That does not mean it is harmless to post publicly.
Internal links can reveal:
- Page names
- Department structures
- Internal tools
- Company terminology
- Restricted document locations
- Information about active programs
Employees should not publish BrightWeb links on public websites, social media, discussion boards, or personal profiles.
When another employee needs the resource, share it through the approved internal channel.
When an external person needs information, use the public Bright Horizons source instead.
Do Not Copy Internal Content Into Public Posts
Employees may sometimes want to share company news on personal social media.
Internal BrightWeb content should not automatically be copied into a public post.
An announcement may contain details intended only for employees, even when the general subject sounds harmless.
Before sharing externally, employees should confirm that:
- The information has been publicly released
- The wording is approved for external use
- No private names or details are included
- The content does not reveal an internal process
- The announcement is still current
A public company page is a safer source for externally shareable information than an internal screenshot.
Use Approved Images
Photographs taken inside a center may include children, families, employees, personal items, or private information in the background.
Employees should not upload images to BrightWeb or share them elsewhere without considering:
- Consent
- Company policy
- Intended audience
- Identifiable children
- Name labels
- Classroom records
- Computer screens
- Personal belongings
- Sensitive situations
An image can reveal more than the person taking it notices.
The background deserves the same review as the main subject.
Avoid Offensive or Discriminatory Content
Professional communication should not include content that insults or targets people based on personal characteristics.
That includes jokes, comments, images, or statements involving:
- Race
- National origin
- Religion
- Disability
- Age
- Sex
- Gender
- Sexual orientation
- Pregnancy
- Family status
- Accent
- Appearance
- Medical condition
Employees may intend a comment as humor.
The effect can still be harmful.
BrightWeb should remain a place where employees can receive company information without encountering harassment or degrading content.
Humor Can Be Misread
Written humor lacks facial expression and tone.
A joke that sounds harmless during an in-person conversation may appear hostile when posted.
Employees should be cautious with humor about:
- Coworker mistakes
- Families
- Children
- Leadership
- Job roles
- Cultural differences
- Workload
- Sensitive incidents
- Private experiences
The wider the audience, the less control the author has over how the message will be interpreted.
When in doubt, leave the joke out.
Do Not Use BrightWeb for Personal Advertising
An internal company portal should not become a marketplace for unrelated personal business.
Unless Bright Horizons has an approved space or policy allowing it, employees should avoid posting:
- Products for sale
- Personal business promotions
- Referral links
- Fundraising campaigns
- Rental offers
- Political campaign material
- Unrelated event promotions
- Repeated requests for personal support
Even a well-intentioned post can place pressure on coworkers who may feel uncomfortable declining.
Company resources should remain focused on company purposes.
Political Arguments Usually Do Not Belong There
Public events may affect employees and the organization.
That does not mean BrightWeb should become a political debate forum.
Employees should avoid using internal company spaces to:
- Campaign for a candidate
- Attack coworkers over political beliefs
- Post unrelated partisan content
- Pressure others to support a cause
- Begin arguments disconnected from work responsibilities
Official company communication about legal, regulatory, safety, or operational changes is different from personal political advocacy.
The distinction is whether the information supports legitimate workplace needs.
Protect Company Documents
Internal documents may contain information that should remain within Bright Horizons.
Employees should avoid:
- Uploading documents to personal cloud storage
- Sending files to a personal email without approval
- Posting documents publicly
- Printing unnecessary copies
- Leaving materials on shared devices
- Sharing files with former employees
- Reusing internal templates outside the company
- Distributing restricted policies
A document does not become public simply because it can be downloaded.
Employees remain responsible for how they handle it afterward.
Be Careful on Shared Devices
A shared computer can expose BrightWeb information to other people.
When using a shared or public device, employees should avoid:
- Saving credentials
- Leaving the session open
- Downloading confidential files
- Allowing the browser to remember information
- Leaving printed materials unattended
- Taking screenshots that remain in a shared folder
The employee should close the session properly and remove any sensitive local files when company rules permit.
A device used by other family members or coworkers deserves extra caution.
Do Not Ask Coworkers to Share Their Credentials
Each employee should use their own authorized account.
Employees should not ask another person to:
- Share credentials
- Open a restricted page
- Download a file on their behalf
- Approve an action using someone else’s account
- Leave a session open for shared use
Different employees may see different content for legitimate reasons.
Bypassing those differences can create security and accountability problems.
If a resource is needed for work, the correct solution is to request proper permission.
Avoid Uploading Unverified Documents
Employees should not add files to an internal space unless they understand what the document is and whether it is current.
Before sharing a file, check:
- Author
- Date
- Version
- Intended audience
- Source
- Whether it has been replaced
- Whether it contains private information
- Whether it is approved for internal distribution
A professional-looking document is not automatically official.
Outdated or unofficial files can spread quickly once others assume they came from an authorized source.
Label Drafts Clearly
A draft can easily be mistaken for final guidance.
When sharing unfinished material, label it clearly:
- Draft
- For Review
- Not Final
- Pending Approval
- Working Copy
Employees should also explain what kind of feedback is needed and who will make the final decision.
Without that context, coworkers may begin following instructions that were never approved.
Correct Inaccurate Information Quickly
A post does not become permanent truth simply because it has already been published.
When information changes or an error is found, employees should:
- Correct the original message when possible.
- State what changed.
- Provide the new information.
- Identify the current document or deadline.
- Notify the affected audience when necessary.
A clear correction is better than hoping people will discover the updated information on their own.
Avoid Deleting Context Without Explanation
Deleting a mistaken post may remove the incorrect statement, but it may also leave coworkers confused.
If people already acted on the message, they need a correction.
A useful update might say:
The earlier announcement was removed because it contained an incorrect date. The correct deadline is August 3.
This provides closure and reduces uncertainty.
Transparency is often more useful than silent removal.
Use the Correct Channel for Urgent Issues
BrightWeb may not be monitored continuously by the person who needs to act.
Employees should not rely on a general internal post for situations involving:
- Immediate child safety
- Medical emergencies
- Security concerns
- Active facility hazards
- Urgent staffing problems
- Time-sensitive incidents
- Threats
- Situations requiring emergency services
Urgent matters should follow the designated immediate-response process.
An internal post can support later communication, but it should not replace direct action.
Formal Reports Belong in Formal Systems
BrightWeb may not be the correct place for official documentation involving:
- Workplace injuries
- Child incidents
- Compliance concerns
- Harassment reports
- Safety violations
- Employee complaints
- Legal matters
- Formal investigations
These situations often have specific forms, reporting lines, and confidentiality requirements.
Posting a summary in the wrong place can expose information and interfere with the formal process.
Employees should use the system designed for that type of report.
Think Before Replying to Everyone
A reply intended for one person can create unnecessary noise when sent to a large audience.
Before responding, ask:
- Does everyone need this answer?
- Is the question specific to me?
- Would a private response be better?
- Does the answer add useful information for the whole group?
- Am I repeating something already stated?
Large internal audiences should receive only information that helps them.
This makes important messages easier to notice.
Avoid Posting the Same Message Repeatedly
Repeated posts can make employees ignore future communication.
Before sending another announcement, consider whether the existing message can be:
- Updated
- Clarified
- Moved to a more appropriate audience
- Summarized
- Referenced in a reminder
Multiple versions of the same information may also create uncertainty about which one is current.
One accurate source is usually better than several slightly different copies.
Common BrightWeb Acceptable Use Questions
Can internal information be shared with a former employee?
Not automatically. Former employees may no longer be authorized to receive company information.
Can I post a screenshot from BrightWeb on social media?
Internal screenshots should not be treated as public content. Use an approved public source for external sharing.
Can I mention a child without using a full name?
Removing a name may not remove every identifying detail. Sensitive information should still follow the correct reporting process.
Can I post a complaint about a coworker?
Personal and performance concerns should generally be handled privately through the appropriate management channel.
Can I share an old BrightWeb announcement?
Check whether the information is still current before reposting it.
Can I use BrightWeb to promote a personal fundraiser?
Only when an approved company policy or designated space clearly permits it.
Is BrightWeb the correct place for an emergency?
No. Immediate safety and emergency situations require direct action through the established emergency process.
A Pre-Posting Checklist
Before publishing or sharing something through BrightWeb, employees should ask:
✅ Is this information accurate?
✅ Is it current?
✅ Does the audience need it?
✅ Does it contain private information?
✅ Is BrightWeb the correct channel?
✅ Could the message embarrass or harm someone?
✅ Am I posting while angry?
✅ Does the content belong to the company?
✅ Am I allowed to share the attachment?
✅ Would a private message be more appropriate?
✅ Is immediate action required somewhere else?
✅ Would I be comfortable explaining this post to my manager?
If any answer creates doubt, pause before publishing.
Examples of Safer Communication
Instead of:
Sarah is out because she is dealing with a medical problem.
Use:
Sarah is unavailable today. Please direct urgent questions to the center leadership team.
Instead of:
This family complains about everything.
Use:
The family has requested clarification about the current process. Leadership is reviewing the concern.
Instead of:
I heard our center is closing next month.
Use:
I have not seen an official update regarding the center. Please rely on communication from leadership.
Instead of:
Michael forgot the report again.
Use:
The report is not yet complete. An updated delivery time will be shared this afternoon.
The safer versions provide necessary workplace information without exposing personal details or blaming individuals.
Why BrightWeb Acceptable Use Matters
Acceptable use is not only about preventing obvious misconduct.
It protects the quality of internal communication.
When employees share accurate, necessary, and respectful information, coworkers can trust what they see. When private details, rumors, emotional posts, and outdated documents appear regularly, that trust disappears.
BrightWeb should help employees understand what is happening and what they need to do.
It should not become a source of gossip, embarrassment, privacy problems, or conflicting instructions.
The most reliable standard is simple:
Share only what supports a legitimate workplace purpose.
Use the correct audience.
Protect private information.
Verify facts.
Choose professional language.
And remember that internal communication still has real consequences for the people being discussed.